@@ -1804,6 +1804,30 @@ General Parameters
1804
1804
.. seealso: :ref:`storage-node-watchdog`
1805
1805
1806
1806
1807
+ .. parameter:: tcmallocAggressiveMemoryDecommit
1808
+
1809
+ *Type*: integer (``0`` or ``1`` only)
1810
+
1811
+ Default: 1
1812
+
1813
+ If you enable ``tmallocAggressiveMemoryDecommit``, MongoDB:
1814
+
1815
+ - releases a :term:`chunk <chunk>` of memory to system, and
1816
+
1817
+ - attempts to return all neighboring free chunks.
1818
+
1819
+ A value of ``1`` enables ``tcmallocAggressiveMemoryDecommit``;
1820
+ ``0`` disables this parameter.
1821
+
1822
+ If you enable this parameter, the system will require new memory allocations
1823
+ for use. Consider enabling ``tcmallocAggressiveMemoryDecommit``
1824
+ only on memory-constrained systems and after pursuing other memory and
1825
+ performance options.
1826
+
1827
+ Despite the potential performance degradation when using
1828
+ ``tcmallocAggressiveMemoryDecommit``, it is often preferred over using
1829
+ :parameter:`tcmallocReleaseRate`.
1830
+
1807
1831
.. parameter:: tcmallocReleaseRate
1808
1832
1809
1833
.. versionadded:: 4.2.3
@@ -1820,6 +1844,12 @@ General Parameters
1820
1844
return memory faster; decrease it to return memory slower.
1821
1845
Reasonable rates are in the range [0,10]."
1822
1846
1847
+ .. note::
1848
+
1849
+ Consider using :parameter:`tcmallocAggressiveMemoryDecommit` instead of
1850
+ :parameter:`tcmallocReleaseRate`, unless you see a significant performance
1851
+ degradation when using ``tcmallocAggressiveMemoryDecommit``.
1852
+
1823
1853
To modify the release rate during run time, you can use the
1824
1854
:dbcommand:`setParameter` command; for example:
1825
1855
0 commit comments