@@ -1719,6 +1719,30 @@ General Parameters
1719
1719
.. seealso: :ref:`storage-node-watchdog`
1720
1720
1721
1721
1722
+ .. parameter:: tcmallocAggressiveMemoryDecommit
1723
+
1724
+ *Type*: integer (``0`` or ``1`` only)
1725
+
1726
+ Default: 1
1727
+
1728
+ If you enable ``tmallocAggressiveMemoryDecommit``, MongoDB:
1729
+
1730
+ - releases a :term:`chunk <chunk>` of memory to system, and
1731
+
1732
+ - attempts to return all neighboring free chunks.
1733
+
1734
+ A value of ``1`` enables ``tcmallocAggressiveMemoryDecommit``;
1735
+ ``0`` disables this parameter.
1736
+
1737
+ If you enable this parameter, the system will require new memory allocations
1738
+ for use. Consider enabling ``tcmallocAggressiveMemoryDecommit``
1739
+ only on memory-constrained systems and after pursuing other memory and
1740
+ performance options.
1741
+
1742
+ Despite the potential performance degradation when using
1743
+ ``tcmallocAggressiveMemoryDecommit``, it is often preferred over using
1744
+ :parameter:`tcmallocReleaseRate`.
1745
+
1722
1746
.. parameter:: tcmallocReleaseRate
1723
1747
1724
1748
.. versionadded:: 4.2.3
@@ -1735,7 +1759,13 @@ General Parameters
1735
1759
return memory faster; decrease it to return memory slower.
1736
1760
Reasonable rates are in the range [0,10]."
1737
1761
1738
- To modify the release rate during runtime, you can use the
1762
+ .. note::
1763
+
1764
+ Consider using :parameter:`tcmallocAggressiveMemoryDecommit` instead of
1765
+ :parameter:`tcmallocReleaseRate`, unless you see a significant performance
1766
+ degradation when using ``tcmallocAggressiveMemoryDecommit``.
1767
+
1768
+ To modify the release rate during run time, you can use the
1739
1769
:dbcommand:`setParameter` command; for example:
1740
1770
1741
1771
.. code-block:: javascript
0 commit comments