[SERVER-16829] Expose tcmalloc runtime configuration options through setParameter mechanism Created: 13/Jan/15  Updated: 13/Sep/21  Resolved: 13/Jan/15

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 2.8.0-rc5

Type: Improvement Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-35046 Add parameter to set tcmalloc aggress... Closed
Related
related to SERVER-17105 Server fails to start under Valgrind:... Closed
is related to SERVER-42697 Expose tcmalloc_release_rate via setP... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

SERVER-16551 and SERVER-16517 both indicate that for many mongodb workloads, the default cap on the size of all per-thread caches imposed by tcmalloc is too low. We should raise the cap, and expose an option to allow the administrator to tune it at start-up and runtime.

Specifically, mongod should present the tcmalloc property tcmalloc.max_total_thread_cache_bytes via a tcmallocMaxTotalThreadCacheBytes argument to setParameter, and tcmalloc.aggressive_memory_decommit via tcmallocAggressiveMemoryDecommit.



 Comments   
Comment by Githook User [ 13/Jan/15 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-16829 Expose tcmalloc configuration options for per-thread cache size and decommit behavior.

Also, increases the default cap on the sum of all per-thread cache sizes from
32MB to 64MB, as advised by SERVER-16551. Should improve behavior of
SERVER-16517, as well.
Branch: master
https://github.com/mongodb/mongo/commit/a6ca16f211fe01d2870593d9ab9bfaaa88097a14

Generated at Thu Feb 08 03:42:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.