about summary refs log tree commit homepage
path: root/lib/PublicInbox/IMAPD.pm
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2024-03-11 19:40:11 +0000
committerEric Wong <e@80x24.org>2024-03-12 06:18:18 +0000
commit298b05cef615ae3d3f1323e805fe135ae5138144 (patch)
tree5eac79948ec406cbc2c6d153d2a31df1c4a2c5f7 /lib/PublicInbox/IMAPD.pm
parent166532d5a7fb7409db8e7877ca961afb60ad28e5 (diff)
downloadpublic-inbox-298b05cef615ae3d3f1323e805fe135ae5138144.tar.gz
I may be mistaken, but I suspect the reason jemalloc handles
long-lived processes better than glibc is due to granularity
reduction being scaled to larger size classes.  This can waste
20% of an individual allocation, but increases the likelyhood
of reuse (without splitting/consolidating into other sizes).

In other words, glibc seems to try too hard to make the best fit
for initial allocations.  This ends up being suboptimal over
time as those allocations are freed and similar (but not
identical) allocations come in.  jemalloc sacrifices the best
initial fit for better fits over a long process lifetime.
Diffstat (limited to 'lib/PublicInbox/IMAPD.pm')
0 files changed, 0 insertions, 0 deletions