-
Type:
New Feature
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.6 Required, 4.0 Required, 4.2.3, 4.3.3
-
Component/s: Internal Code
-
Labels:
-
Backwards Compatibility:Fully Compatible
-
Backport Requested:v4.2, v4.0, v3.6
-
Epic Link:
-
Sprint:Performance 2019-12-02, Performance 2019-12-16
SERVER-16829 exposed tcmalloc_aggressive_decommit via the setParameter framework. This has turned out to be not very useful, as aggressive decommit comes with a huge performance penalty. (-75% in a small YCSB workload.)
We recently found that tcmalloc_release_rate can be used to reduce memory overhead, with little or no performance overhead. We should add a setParameter knob to do this at runtime too.
Relevant tcmalloc documentation
Example:
db.adminCommand({setParameter: 1, tcmallocReleaseRate: 10})
|
- depends on
-
SERVER-46898 The tcmallocReleaseRate parameter does not work in 4.0 and 3.6
-
- Closed
-
- is documented by
-
DOCS-13271 Investigate changes in SERVER-42697: Expose tcmalloc_release_rate via setParameter
-
- Closed
-
- related to
-
SERVER-16829 Expose tcmalloc runtime configuration options through setParameter mechanism
-
- Closed
-