[SERVER-84298] Fix up memory accounting in query stats store Created: 19/Dec/23 Updated: 19/Jan/24 Resolved: 19/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Erin Zhu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | flag-for-2885-backport | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||
| Description |
|
erin.zhu@mongodb.com and I noticed some mis-accounting going on while investigating a performance BF which might have been partially attributable to us starting to store more query stats, even though we are using the same-ish amount of space (after/around This ticket tracks the work to better account for space used, and to add some more testing around it. Specifically, I noticed:
|
| Comments |
| Comment by Githook User [ 18/Jan/24 ] |
|
Author: {'name': 'erinzhu001', 'email': 'erin.zhu@mongodb.com', 'username': 'erinzhu001'}Message: GitOrigin-RevId: 8b2c64a3d46b50d3b16f06d00dcff9197e48aaa5 |
| Comment by Charlie Swanson [ 20/Dec/23 ] |
|
Punting this out of PM-2885 and leaving assigned to erin.zhu@mongodb.com to resolve. We are closing the epic since all customer-focused work is complete. |