@@ -1844,6 +1844,30 @@ General Parameters
1844
1844
.. seealso: :ref:`storage-node-watchdog`
1845
1845
1846
1846
1847
+ .. parameter:: tcmallocAggressiveMemoryDecommit
1848
+
1849
+ *Type*: integer (``0`` or ``1`` only)
1850
+
1851
+ Default: 1
1852
+
1853
+ If you enable ``tmallocAggressiveMemoryDecommit``, MongoDB:
1854
+
1855
+ - releases a :term:`chunk <chunk>` of memory to system, and
1856
+
1857
+ - attempts to return all neighboring free chunks.
1858
+
1859
+ A value of ``1`` enables ``tcmallocAggressiveMemoryDecommit``;
1860
+ ``0`` disables this parameter.
1861
+
1862
+ If you enable this parameter, the system will require new memory allocations
1863
+ for use. Consider enabling ``tcmallocAggressiveMemoryDecommit``
1864
+ only on memory-constrained systems and after pursuing other memory and
1865
+ performance options.
1866
+
1867
+ Despite the potential performance degradation when using
1868
+ ``tcmallocAggressiveMemoryDecommit``, it is often preferred over using
1869
+ :parameter:`tcmallocReleaseRate`.
1870
+
1847
1871
.. parameter:: tcmallocReleaseRate
1848
1872
1849
1873
.. versionadded:: 4.2.3
@@ -1860,6 +1884,12 @@ General Parameters
1860
1884
return memory faster; decrease it to return memory slower.
1861
1885
Reasonable rates are in the range [0,10]."
1862
1886
1887
+ .. note::
1888
+
1889
+ Consider using :parameter:`tcmallocAggressiveMemoryDecommit` instead of
1890
+ :parameter:`tcmallocReleaseRate`, unless you see a significant performance
1891
+ degradation when using ``tcmallocAggressiveMemoryDecommit``.
1892
+
1863
1893
To modify the release rate during run time, you can use the
1864
1894
:dbcommand:`setParameter` command; for example:
1865
1895
0 commit comments