We are seeing some regressions in "Queries.IdentityView.UnindexedLargeInMatching", which probably are caused by us adding an additional parse of an expensive $in query. We should run some benchmarking to confirm the waste and then look to see if there's any way to avoid a re-parse between the query stats store and when we hand it off to run the view as an aggregation.