project-base/server-skynet-source-3rd-jemalloc
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove the lg_tcache_gc_sweep option.

Browse Source 
Remove the lg_tcache_gc_sweep option, because it is no longer
very useful.  Prior to the addition of dynamic adjustment of tcache fill
count, it was possible for fill/flush overhead to be a problem, but this
problem no longer occurs.
This commit is contained in:
Jason Evans
2012-03-05 14:34:37 -08:00
parent b8c8be7f8a
commit 4507f34628
6 changed files with 12 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/jemalloc.xml.in
View File

@@ -853,29 +853,11 @@ malloc_conf = "xmalloc:true";]]></programlisting>
allocations to be satisfied without performing any thread
synchronization, at the cost of increased memory use. See the
<link
linkend="opt.lg_tcache_gc_sweep"><mallctl>opt.lg_tcache_gc_sweep</mallctl></link>
and <link
linkend="opt.lg_tcache_max"><mallctl>opt.lg_tcache_max</mallctl></link>
options for related tuning information. This option is enabled by
option for related tuning information. This option is enabled by
default.</para></listitem>
</varlistentry>
<varlistentry id="opt.lg_tcache_gc_sweep">
<term>
<mallctl>opt.lg_tcache_gc_sweep</mallctl>
(<type>ssize_t</type>)
<literal>r-</literal>
[<option>--enable-tcache</option>]
</term>
<listitem><para>Approximate interval (log base 2) between full
thread-specific cache garbage collection sweeps, counted in terms of
thread-specific cache allocation/deallocation events. Garbage
collection is actually performed incrementally, one size class at a
time, in order to avoid large collection pauses. The default sweep
interval is 8192 (2^13); setting this option to -1 will disable garbage
collection.</para></listitem>
</varlistentry>
<varlistentry id="opt.lg_tcache_max">
<term>
<mallctl>opt.lg_tcache_max</mallctl>