@@ -1532,6 +1532,30 @@ General Parameters
1532
1532
.. seealso: :ref:`storage-node-watchdog`
1533
1533
1534
1534
1535
+ .. parameter:: tcmallocAggressiveMemoryDecommit
1536
+
1537
+ *Type*: integer (``0`` or ``1`` only)
1538
+
1539
+ Default: 1
1540
+
1541
+ If you enable ``tmallocAggressiveMemoryDecommit``, MongoDB:
1542
+
1543
+ - releases a :term:`chunk <chunk>` of memory to system, and
1544
+
1545
+ - attempts to return all neighboring free chunks.
1546
+
1547
+ A value of ``1`` enables ``tcmallocAggressiveMemoryDecommit``;
1548
+ ``0`` disables this parameter.
1549
+
1550
+ If you enable this parameter, the system will require new memory allocations
1551
+ for use. Consider enabling ``tcmallocAggressiveMemoryDecommit``
1552
+ only on memory-constrained systems and after pursuing other memory and
1553
+ performance options.
1554
+
1555
+ Despite the potential performance degradation when using
1556
+ ``tcmallocAggressiveMemoryDecommit``, it is often preferred over using
1557
+ :parameter:`tcmallocReleaseRate`.
1558
+
1535
1559
.. parameter:: tcmallocReleaseRate
1536
1560
1537
1561
.. versionadded:: 4.2.3
@@ -1548,7 +1572,13 @@ General Parameters
1548
1572
return memory faster; decrease it to return memory slower.
1549
1573
Reasonable rates are in the range [0,10]."
1550
1574
1551
- To modify the release rate during runtime, you can use the
1575
+ .. note::
1576
+
1577
+ Consider using :parameter:`tcmallocAggressiveMemoryDecommit` instead of
1578
+ :parameter:`tcmallocReleaseRate`, unless you see a significant performance
1579
+ degradation when using ``tcmallocAggressiveMemoryDecommit``.
1580
+
1581
+ To modify the release rate during run time, you can use the
1552
1582
:dbcommand:`setParameter` command; for example:
1553
1583
1554
1584
.. code-block:: javascript
0 commit comments