[TEST] Use global Rust jemalloc#155673
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[TEST] Use global Rust jemalloc
|
💔 Test for 64c00df failed: CI. Failed job:
|
This comment has been minimized.
This comment has been minimized.
|
On macOS 11:
|
|||||||||||||||||||||||||||||||||||||||||||||||
|
|
||
| #[cfg(feature = "jemalloc")] | ||
| #[global_allocator] | ||
| static GLOBAL: tikv_jemallocator::Jemalloc = tikv_jemallocator::Jemalloc; |
There was a problem hiding this comment.
This only works when libstd is statically linked into librustc_driver which we don't do on MinGW:
rust/src/bootstrap/src/core/builder/mod.rs
Lines 1125 to 1129 in 92c7010
-Zdefault-visibility=protected the default in the future). Rustc should probably emit an error for this case, but does not do so currently.
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[TEST] Use global Rust jemalloc
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (ca3fc89): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking 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. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.1%, secondary 0.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 1.7%, secondary 0.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 487.764s -> 489.254s (0.31%) |
No description provided.