-
Notifications
You must be signed in to change notification settings - Fork 19
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
try using the system allocator #26
Comments
Note: This only works on nightly, so it doesn't work for us. However, configuring jemalloc might. I'm looking into that next. |
With rust-lang/rust#51241 available since two releases (or three releases in few days) this should be considered again. If machine running the benchmarks has fairly recent glibc (at least 2.26) this could bring nice speedup. |
Apart from the binary_trees benchmark, which uses an arena anyway, none of the benchmarks allocate enough to make any difference, apart from reducing the base profile a bit. |
On r/rust, Alex Chrichton suggested we can use the system allocator.
This would presumably rid us of the 6MB upfront allocation of jemalloc, and make Rust look leaner in the benchmarks, so I'd like to benchmark this once I get to my PC.
The text was updated successfully, but these errors were encountered: