[SERVER-81827] Investigate agg $in regressions with query stats Created: 03/Oct/23  Updated: 27/Oct/23  Resolved: 04/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Will Buerger Assignee: Alyssa Clark
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-85082 M2 Performance Report Closed
Participants:

 Description   

The following test cases are showing throughput regressions notably worse than the average regressions across other query shapes:

  • Aggregation.StringUnindexedInPredWithSimpleCollation 10.11%
  • Aggregation.UnindexedLargeInNonMatching 9.84%
  • Aggregation.UnindexedLargeInMatching 9.54%
  • Aggregation.UnindexedVeryLargeInSortedMatching 7.75%
  • Aggregation.StringUnindexedInPredWithSimpleCollation (name doesn't reflect but it does have an $in) 7.64%

 

SERVER-80468 addressed a regression related to large $in lists. We should make sure the fix from that ticket is being used on agg path, and investigate the cause of these regressions.


Generated at Thu Feb 08 06:47:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.