[SERVER-71140] Reconsider the string size in mongo-perf $sortArray workload pipelines.js Created: 07/Nov/22 Updated: 16/Mar/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: | |
| Story Points: | 2 |
| Description |
|
The $sortArray workloads running in pipelines.js create documents with arrays of 1 character sized strings. This makes the difference internally between taking a deep copy or shallow copy for $sortArray and the performance changes. If 1 character sized strings are not reasonable, perhaps we should update the workload to use larger strings |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 07/Nov/22 ] |
|
Also consider tweaking the relevant metric names, to 'reset' the workload as new, rather than continuing under the old name and making the workload changes appear as if there were a performance regression or improvement. |