jemalloc: upgrade from 3.6.0 to 5.3.1 - #1096
Draft
kenhys wants to merge 1 commit into
Draft
Conversation
kenhys
force-pushed
the
jemalloc531
branch
3 times, most recently
from
July 27, 2026 07:31
03bf43c to
815684f
Compare
Contributor
Author
|
Recently checked memory usage trends: RSS and PSS 
|
Contributor
Author
|
Another aspects : ref fluent/fluentd#1657 
|
Contributor
Author
|
in_tail with 1 GB file (rake benchmark:run:in_tail with fluent-package-builder master) It seems that total execution time takes a bit longer for jemalloc 5.3.1+MALLOC_CONF. jemalloc 3.6.0 jemalloc 5.3.1 vanilla jemalloc 5.3.1 + MALLOC_CONF tuning |
In the historical reasons, there are memory consumption issue between 4.x and 5.2.x for fluent-package. There are trade off about memory usage and performance, see MALLOC_CONF parameters in details: https://gist.github.com/jjb/9ff0d3f622c8bbe904fe7a82e35152fc With dirty_decay_ms:0, it behaves similar to 3.6.0, but you must pay performance penalty. dirty_decay_ms:1000 might be conservative approach for performance and memory usage, but it tends to use more memory in contrast to 3.6.0. dirty_decay_ms:400 strikes a well-balanced between memory usage and performance. (That situation might be changed in future jemalloc release or other practical benchmarks) Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
Contributor
Author
|
With dirty_decay_ms:0, it behaves similar to 3.6.0, but you must pay |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the historical reasons, there are memory consumption issue between 4.x and 5.2.x for fluent-package.
Since 5.3.x, the situation seems changed about that issue, upgrade it from 3.6.0.
There are trade of about memory and performance, adopted already tuned MALLOC_CONF parameters from here:
https://gist.github.com/jjb/9ff0d3f622c8bbe904fe7a82e35152fc