[SERVER-80242] Investivate wildcard index read performance under query stats Created: 18/Aug/23  Updated: 02/Oct/23  Resolved: 02/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Joshua Lapacik (Inactive) Assignee: Joshua Lapacik (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File no-query-stats.svg     File wildcard_index_read_no_query_stats.svg     File wildcard_index_read_query_stats.svg     File with-query-stats.svg    
Issue Links:
Depends
is depended on by SERVER-85055 Tracking: M1 Performance improvement ... Closed
Assigned Teams:
Query Optimization
Sprint: QO 2023-09-04, QO 2023-09-18, QO 2023-10-02, QO 2023-10-16
Participants:

 Description   

query-stats-microbench-standalone
wildcard-index-read_read_commands

Test|Regression
----------------
Queries.WildcardIndex.RangeQueryOnMultipleFields|-10%|
Queries.WildcardIndex.RangeQueryOnMultipleFields.Baseline|-10%
Queries.WildcardIndex.RangeQueryMultipleFieldsWithSortOnSingleField.Baseline|-10%



 Comments   
Comment by Charlie Swanson [ 02/Oct/23 ]

Thanks joshua.lapacik@mongodb.com for the efforts and providing the flame graphs. I think we should close this one out as "not worth it". I just found the test file: https://github.com/mongodb/mongo-perf/blob/79cc3c7e00dda5590c1806aa40fd88bdea33e8b9/testcases/wildcard_index_query.js#L248 

 

It looks like those tests are running with only 100 documents in the collection... what a weird test. I suspect this regression will improve on larger data sets and I think it is not that worthy of digging into. I'll add a quick note to the performance report and close this out.

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