[SERVER-71170] [CQF] Consider CQF coverage in profile_operation_metrics.js Created: 08/Nov/22 Updated: 11/Jul/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hana Pearlman | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
The profile_operation_metrics.js test currently fails when run with CQF enabled because the docBytesRead metric for read operations using cqf are reported as higher than tests expect. The reason is twofold: 1) sometimes bonsai chooses a collscan when an index scan is expected by the test, and 2) when we use the sampling CE mode (the current default mode), this can increase the docBytesRead metric for the entire query. We should consider whether we want to change the existing test or add a new test which can give us resource consumption metric coverage for CQF. |
| Comments |
| Comment by David Percy [ 16/Nov/22 ] |
|
This sounds like an integration feature: probably a better fit for PM-2651. I think testing things like metrics and resource consumption fall in that category. |
| Comment by Ana Meza [ 15/Nov/22 ] |
|
david.percy@mongodb.com would you be ok with adding this ticket to PM-2516? |