Run apache2 under jemalloc#7858
Draft
legoktm wants to merge 1 commit into
Draft
Conversation
jemalloc ends up resolving the memory fragmentation issues we've seen under APIv2 with the default glibc allocator. It should be relatively safe to swap in given how battle tested jemalloc is by much larger corporate users. See <freedomofpress/securedrop-client#3234 (comment)> and following comments. Fixes #7817.
Member
Author
|
I'm not seeing the same gains (or any gains whatsoever tbh) from using jemalloc on the server, maybe I misconfigured something this time around, or possibly the initial test wasn't accurate? I'll have to spend some more time on this. |
Member
|
If #7862 is right, there may still be a higher-level optimization to pursue.... |
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
2 participants
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.
jemalloc ends up resolving the memory fragmentation issues we've seen under APIv2 with the default glibc allocator.
It should be relatively safe to swap in given how battle tested jemalloc is by much larger corporate users.
See freedomofpress/securedrop-client#3234 (comment) and following comments.
Fixes #7817.
Test plan
Checklist
This change accounts for: