Skip to content

Update jemalloc to 5.4.0 - #162965

Draft
mati865 wants to merge 1 commit into
rust-lang:mainfrom
mati865:push-rwvmyxvwkwnv
Draft

mati865 wants to merge 1 commit into
rust-lang:mainfrom
mati865:push-rwvmyxvwkwnv

Conversation

@mati865

@mati865 mati865 commented Sep 18, 2026 •

Copy link
Copy Markdown
Member

@rustbot rustbot added A-tidy Area: The tidy tool S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Sep 18, 2026
@mati865

mati865 commented Sep 18, 2026

Copy link
Copy Markdown
Member Author

@bors try @rust-timer queue

@rust-timer

This comment has been minimized.

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Sep 18, 2026
rust-bors Bot pushed a commit that referenced this pull request Sep 18, 2026
@rust-bors

This comment has been minimized.

@rust-bors

rust-bors Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: 59272b4 (59272b41d288dc8a35163bc03f4ad3d195b70b01)
Base parent: 498b89d (498b89dd40af107a23c13a009345a0dea224248c)

@rust-timer

This comment has been minimized.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (59272b4): comparison URL.

Overall result: ❌✅ regressions and improvements - please read:

Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf.

Next, please: If you can, justify the regressions found in this try perf run in writing along with @rustbot label: +perf-regression-triaged. If not, fix the regressions and do another perf run. Neutral or positive results will clear the label automatically.

@bors rollup=never rustc-perf
@rustbot label: -S-waiting-on-perf +perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
0.3% [0.1%, 0.9%] 20
Regressions ❌
(secondary)
0.4% [0.0%, 1.1%] 94
Improvements ✅
(primary)
-0.5% [-1.9%, -0.1%] 44
Improvements ✅
(secondary)
-0.6% [-1.4%, -0.1%] 42
All ❌✅ (primary) -0.2% [-1.9%, 0.9%] 64

Max RSS (memory usage)

Results (primary 3.1%, secondary 4.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
3.1% [0.6%, 8.5%] 204
Regressions ❌
(secondary)
4.6% [0.7%, 17.3%] 125
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.8% [-5.4%, -0.6%] 6
All ❌✅ (primary) 3.1% [0.6%, 8.5%] 204

Cycles

Results (primary 2.1%, secondary 13.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
2.1% [2.1%, 2.1%] 1
Regressions ❌
(secondary)
16.3% [2.0%, 28.4%] 14
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.9% [-3.4%, -2.4%] 2
All ❌✅ (primary) 2.1% [2.1%, 2.1%] 1

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 497.674s -> 496.406s (-0.25%)
Artifact size: 408.91 MiB -> 406.94 MiB (-0.48%)

@rustbot rustbot added perf-regression Performance regression. and removed S-waiting-on-perf Status: Waiting on a perf run to be completed. labels Sep 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-tidy Area: The tidy tool perf-regression Performance regression. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants