Merged
Conversation
olix0r
added a commit
to linkerd/linkerd2
that referenced
this pull request
Oct 22, 2021
This release changes the default allocator (on linux/x86_64) to be `jemalloc`. In tests, jemalloc proves to use less memory without noticeable impacts on CPU utilization or latency. This change also includes dependency updates, including an update of Rust to v1.56.0. --- * build(deps): bump tower from 0.4.9 to 0.4.10 (linkerd/linkerd2-proxy#1320) * Adopt Rust edition 2021 (linkerd/linkerd2-proxy#1295) * Use jemalloc (linkerd/linkerd2-proxy#1321) * Disable incremental compilation in CI (linkerd/linkerd2-proxy#1322) * build(deps): bump h2 from 0.3.6 to 0.3.7 (linkerd/linkerd2-proxy#1324) * build(deps): bump http-body from 0.4.3 to 0.4.4 (linkerd/linkerd2-proxy#1325) * build(deps): bump hyper from 0.14.13 to 0.14.14 (linkerd/linkerd2-proxy#1326)
olix0r
added a commit
that referenced
this pull request
Oct 22, 2021
In load tests, it appears that jemalloc is--perhaps unsurprisingly--more efficient than the alternatives. Specifically, jemalloc uses less memory and is more responsive to memory being released without substantially impacting latency or CPU usage. This is only enabled on `x86_64-unknown-linux-gnu`, as this is the only platform on which all tests pass, etc (per [gnzlbg/jemallocator][readme]). [readme]: https://github.com/gnzlbg/jemallocator/tree/c27a859e98e3cb790dc269773d9da71a1e918458#platform-support
alpeb
pushed a commit
to linkerd/linkerd2
that referenced
this pull request
Oct 25, 2021
This release changes the default allocator (on linux/x86_64) to be `jemalloc`. In tests, jemalloc proves to use less memory without noticeable impacts on CPU utilization or latency. This change also includes dependency updates, including an update of Rust to v1.56.0. --- * build(deps): bump tower from 0.4.9 to 0.4.10 (linkerd/linkerd2-proxy#1320) * Adopt Rust edition 2021 (linkerd/linkerd2-proxy#1295) * Use jemalloc (linkerd/linkerd2-proxy#1321) * Disable incremental compilation in CI (linkerd/linkerd2-proxy#1322) * build(deps): bump h2 from 0.3.6 to 0.3.7 (linkerd/linkerd2-proxy#1324) * build(deps): bump http-body from 0.4.3 to 0.4.4 (linkerd/linkerd2-proxy#1325) * build(deps): bump hyper from 0.14.13 to 0.14.14 (linkerd/linkerd2-proxy#1326)
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.
In load tests, it appears that jemalloc is--perhaps unsurprisingly--more efficient
than the alternatives. Specifically, jemalloc uses less memory and is more responsive
to memory being released without substantially impacting latency or CPU usage.
This is only enabled on
x86_64-unknown-linux-gnu, as this is the only platformon which all tests pass, etc (per gnzlbg/jemallocator).
jemalloc vs system allocator vs mimalloc