[Experiment] Replace jemalloc with mimalloc beta branch

[fee1-dead]

Like #92249 but uses the improved branch to test out max-rss regression

r? @ghost

[fee1-dead]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit eb2a635 with merge d80254e2b2c9678b15cb8bc1950a01d08b59b706...

[bors]

💔 Test failed - checks-actions

[fee1-dead]

@bors try

[bors]

⌛ Trying commit 2775e9e with merge dcee12e0ea11b4bb2057b3a2d79b33cf752ce689...

[fee1-dead]

Not sure what has happened but I don't know why the last try build was still using outdated versions.

@bors try

[bors]

⌛ Trying commit 2775e9e with merge 4dc9cad6d0c28e39b1ea26eb8b43892606dc56b8...

[bors]

☀️ Try build successful - checks-actions
Build commit: 4dc9cad6d0c28e39b1ea26eb8b43892606dc56b8 (4dc9cad6d0c28e39b1ea26eb8b43892606dc56b8)

[rust-timer]

Queued 4dc9cad6d0c28e39b1ea26eb8b43892606dc56b8 with parent f8abed9, future comparison URL.

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[rust-timer]

Finished benchmarking commit (4dc9cad6d0c28e39b1ea26eb8b43892606dc56b8): comparison url.

Summary: This change led to very large relevant mixed results 🤷 in compiler performance.

• Moderate improvement in instruction counts (up to -1.9% on incr-unchanged builds of deeply-nested)
• Very large regression in instruction counts (up to 9.8% on full builds of many-assoc-items)

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 led to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

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

[bjorn3]

This is now a regression for inst count but an improvement for max-rss.

[the8472]

The wall-time results look worse than the instructions.