-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update jemalloc to v5.3 #96790
Update jemalloc to v5.3 #96790
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 4a3f0b89c6d0733a6e84288e3f9aafdf8429875e with merge 7c1ccf45f83f6c96b0fa945d58b116bea4b726ad... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit e0907118f66e205a81a91c7e565ccd847e0ec58f with merge c236f4668dec3cbb6ae05f72d8339c85657b43ff... |
☀️ Try build successful - checks-actions |
Queued c236f4668dec3cbb6ae05f72d8339c85657b43ff with parent 77652b9, future comparison URL. |
Finished benchmarking commit (c236f4668dec3cbb6ae05f72d8339c85657b43ff): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit e61073ef87eed391e23ae16ba5ff037031730411 with merge 41e4c1342cf9326b60d0500f5890059a3d4583fc... |
☀️ Try build successful - checks-actions |
Queued 41e4c1342cf9326b60d0500f5890059a3d4583fc with parent 08b4f1b, future comparison URL. |
Finished benchmarking commit (41e4c1342cf9326b60d0500f5890059a3d4583fc): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit adab135 with merge 9ca7ce57dc5f41875f4d4bf4a239170463384666... |
The perf.rlo queue has a few PRs already, so final perf results should be available in a while. After this last sanity check, r? @Mark-Simulacrum maybe ? (feel free to re-roll if you don't have time) |
So |
@bors delegate=lqd |
✌️ @lqd can now approve this pull request |
☀️ Try build successful - checks-actions |
Queued 9ca7ce57dc5f41875f4d4bf4a239170463384666 with parent 9fadabc, future comparison URL. |
@nnethercote The situation is a bit unclear to me: the owners of the It seems that depending on which of these I'm under the impression that in the most common cases, the end result indeed behaves as an alias. And otherwise in the rarer cases where you depend on more than these main crates, you would see that it's the same code published under 2 different names, with the satellite crates likely depending on the |
Finished benchmarking commit (9ca7ce57dc5f41875f4d4bf4a239170463384666): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
Very nice improvements on max-rss. |
I'll let mark weigh in on whether we need to do some additional checks when updating such important dependencies, that's why I'm not going to r=you immediately, to give him some time to do so. |
We're pretty early in the release cycle and I think this looks like a good win without major regressions, so I think we can move forward. @bors r+ rollup=never |
📌 Commit adab135 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (ebbcbfc): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Now that
jemalloc
version 5.3 has been released, this PR updatestikv-jemalloc-sys
to the corresponding release.The crates.io publishing issue seems to have been resolved for the
jemalloc-sys
package, and version 5.3.0 is now also available under the historical name (and should become the preferred crate to be used). Therefore, this PR also switches back to usingjemalloc-sys
instead oftikv-jemalloc-sys
.