about summary refs log tree commit homepage
path: root/Documentation/public-inbox-tuning.pod
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2024-05-14 06:38:06 +0000
committerEric Wong <e@80x24.org>2024-05-14 22:08:14 +0000
commitc372f2c24d64435c303024f103aac99e37ffb0b4 (patch)
treee25a75cf641a83660bb2eec27f4b91df00e33054 /Documentation/public-inbox-tuning.pod
parent43f890ecda3e1e7d8c55c8a9173d1c430339bcd8 (diff)
downloadpublic-inbox-master.tar.gz
My 32-bit server seems less happy with jemalloc; likely since
munmap is creating holes and it's not using sbrk by default.
jemalloc seems to need large VM space (not actual memory)
to work well, and that isn't a possibility for constrained
32-bit systems.
Diffstat (limited to 'Documentation/public-inbox-tuning.pod')
-rw-r--r--Documentation/public-inbox-tuning.pod7
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/public-inbox-tuning.pod b/Documentation/public-inbox-tuning.pod
index 892ee0f2..b56c2b10 100644
--- a/Documentation/public-inbox-tuning.pod
+++ b/Documentation/public-inbox-tuning.pod
@@ -166,9 +166,10 @@ capacity planning.
 Bursts of small object allocations late in process life contribute to
 fragmentation of the heap due to arenas (slabs) used internally by Perl.
 glibc malloc users should use C<MALLOC_MMAP_THRESHOLD_=131072> to reduce
-fragmentation from the sliding mmap window.  jemalloc (tested as an
-LD_PRELOAD on GNU/Linux) also reduces fragmentation compared to an
-unconfigured glibc malloc in long-lived processes.
+fragmentation from the sliding mmap window.  On 64-bit systems, jemalloc
+(tested as an LD_PRELOAD on GNU/Linux) reduces fragmentation at the
+expense of VM space.  32-bit systems may be better off sticking with
+glibc and MALLOC_MMAP_THRESHOLD_.
 
 =head2 Other OS tuning knobs