Skip to content

test jemalloc 5.3.1#155400

Closed
mati865 wants to merge 2 commits intorust-lang:mainfrom
mati865:push-lktzzwxsklsz
Closed

test jemalloc 5.3.1#155400
mati865 wants to merge 2 commits intorust-lang:mainfrom
mati865:push-lktzzwxsklsz

Conversation

@mati865
Copy link
Copy Markdown
Member

@mati865 mati865 commented Apr 16, 2026

No description provided.

@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 Apr 16, 2026
@mati865
Copy link
Copy Markdown
Member Author

mati865 commented Apr 16, 2026

@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 Apr 16, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Apr 16, 2026
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors Bot commented Apr 16, 2026

☀️ Try build successful (CI)
Build commit: ff8f2e5 (ff8f2e5241b4f46d1f09c01402745b8b5af03be7, parent: 18b439f84ec0b087283bac3356a1eeac53c60c5e)

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (ff8f2e5): 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
@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.2%, 0.5%] 61
Regressions ❌
(secondary)
0.5% [0.0%, 1.1%] 81
Improvements ✅
(primary)
-0.5% [-1.0%, -0.2%] 21
Improvements ✅
(secondary)
-0.3% [-1.1%, -0.0%] 30
All ❌✅ (primary) 0.1% [-1.0%, 0.5%] 82

Max RSS (memory usage)

Results (primary 3.3%, secondary 4.9%)

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

mean range count
Regressions ❌
(primary)
3.3% [0.8%, 12.0%] 204
Regressions ❌
(secondary)
5.3% [0.7%, 17.4%] 103
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-5.3% [-11.3%, -2.8%] 4
All ❌✅ (primary) 3.3% [0.8%, 12.0%] 204

Cycles

Results (primary -2.4%, secondary 0.6%)

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

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
4.6% [2.4%, 5.9%] 5
Improvements ✅
(primary)
-2.4% [-2.4%, -2.4%] 1
Improvements ✅
(secondary)
-3.4% [-5.5%, -1.3%] 5
All ❌✅ (primary) -2.4% [-2.4%, -2.4%] 1

Binary size

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

Bootstrap: 492.463s -> 488.358s (-0.83%)
Artifact size: 394.15 MiB -> 394.40 MiB (0.07%)

@rustbot rustbot added perf-regression Performance regression. and removed S-waiting-on-perf Status: Waiting on a perf run to be completed. labels Apr 16, 2026
@bjorn3
Copy link
Copy Markdown
Member

bjorn3 commented Apr 17, 2026

Wall time is terrible. There are regressions as much as 25%.

@lqd
Copy link
Copy Markdown
Member

lqd commented Apr 17, 2026

the noise threshold is 25% on some of these benchmarks so I wouldn't necessarily use that as a strong proof.
image

thankfully everything else is also bad enough that we don't need wall-times to judge

@mati865
Copy link
Copy Markdown
Member Author

mati865 commented Apr 18, 2026

@bors try @rust-timer queue

@rust-timer

This comment has been minimized.

@rust-bors

This comment has been minimized.

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

rust-bors Bot commented Apr 18, 2026

☀️ Try build successful (CI)
Build commit: c25ed12 (c25ed12e3f021b425f317b56f7218b474268b190, parent: 7a38981b365e4c3672053b910fce9a14c6555ab9)

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (c25ed12): 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
@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.2%, 0.5%] 52
Regressions ❌
(secondary)
0.4% [0.1%, 0.9%] 74
Improvements ✅
(primary)
-0.5% [-1.0%, -0.2%] 21
Improvements ✅
(secondary)
-0.3% [-1.1%, -0.0%] 25
All ❌✅ (primary) 0.1% [-1.0%, 0.5%] 73

Max RSS (memory usage)

Results (primary 3.5%, secondary 4.6%)

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

mean range count
Regressions ❌
(primary)
3.5% [0.8%, 9.7%] 215
Regressions ❌
(secondary)
4.9% [0.6%, 17.5%] 128
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-5.4% [-10.7%, -2.5%] 3
All ❌✅ (primary) 3.5% [0.8%, 9.7%] 215

Cycles

Results (primary -1.8%, secondary 5.1%)

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

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
7.4% [6.6%, 8.2%] 3
Improvements ✅
(primary)
-1.8% [-1.8%, -1.8%] 1
Improvements ✅
(secondary)
-1.8% [-1.8%, -1.8%] 1
All ❌✅ (primary) -1.8% [-1.8%, -1.8%] 1

Binary size

Results (secondary -0.1%)

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

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.1% [-0.1%, -0.1%] 7
All ❌✅ (primary) - - 0

Bootstrap: 492.147s -> 505.437s (2.70%)
Artifact size: 394.26 MiB -> 394.44 MiB (0.05%)

@rustbot rustbot removed the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Apr 18, 2026
@mati865 mati865 closed this May 3, 2026
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label May 3, 2026
@mati865 mati865 deleted the push-lktzzwxsklsz branch May 3, 2026 18:54
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. 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.

5 participants