[SERVER-39402] add a --memorySize option to mongod for limiting memory usage Created: 06/Feb/19  Updated: 28/Aug/23

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

Type: Improvement Priority: Minor - P4
Reporter: Geert Bosch Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Participants:
Case:

 Description   

Currently we default the WiredTiger cache size based on the total amount of memory in the host. However, this doesn't work well when running multiple instances of mongod on the same host. The new option will also make it better possible to size other internal memory structures, such as the TCMalloc thread cache, based on available memory without requiring exposing all such details to the user.

The --memorySize option allows one simple setting to communicate intent to limit total memory usage of mongod to the given number.



 Comments   
Comment by Connie Chen [ 15/Nov/22 ]

michael.gargiulo@mongodb.com - we're thinking of backlogging this, but from the product perspective what is the priority for this?

Comment by Connie Chen [ 09/Nov/22 ]

Throwing this back into "needs scheduling" to be re-triaged as we are closing PM-1725 as won't do since it has been superseded by PM-3007

Generated at Thu Feb 08 04:51:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.