[SERVER-83939] Reduce the memory footprint of the mongod executable Created: 06/Dec/23  Updated: 18/Jan/24

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

Type: Improvement Priority: Major - P3
Reporter: Justin Seyster Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query Execution
Participants:
Linked BF Score: 120

 Description   

Many of our CPU-bound performance workloads get gradually slower over time even when there are no significant changes to the workload's hot code paths. One possibility is that the steadily increasing size of the the mongos and mongod executables make their performance more sensitive to i-cache efficiency.

One good way to test this effect (if it is real) would be to run some of these workloads on a mongod that has been stripped down to remove functionality that they do not use and see if it improves any of the benchmark numbers.

If there is a significant effect, it may be possible to get the same benefit in practice by breaking large features into separate dynamic libraries, which will never get loaded if a user does not use the feature.


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