[SERVER-74558] Profile whether the memory usage check in the $percentile accumulator is a problem Created: 02/Mar/23 Updated: 27/Oct/23 Resolved: 13/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Irina Yatsenko (Inactive) | Assignee: | Backlog - Query Integration |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, the check is done on each input, which isn't really necessary as all our memory usage is a "best effort" estimation and the limits are usually in terms of MB while the changes in usage are likely to be in bytes. If asking for memory usage shows up in profiles, consider:
|
| Comments |
| Comment by Irina Yatsenko (Inactive) [ 13/Mar/23 ] | |
|
I don't think it's going to be a problem. The early profiling on a collection with 1e7 documents shows:
I'm going to close this ticket on the assumption that as we finalize the accumulator and keep profiling it, if the memory check becomes more prominent, we'd notice. |