Skip to content
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

Open
llogiq opened this issue Oct 17, 2015 · 3 comments
Open

try using the system allocator #26

llogiq opened this issue Oct 17, 2015 · 3 comments

Comments

@llogiq
Copy link
Contributor

llogiq commented Oct 17, 2015

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.

@llogiq
Copy link
Contributor Author

llogiq commented Oct 19, 2015

Note: This only works on nightly, so it doesn't work for us. However, configuring jemalloc might. I'm looking into that next.

@mati865
Copy link

mati865 commented Sep 10, 2018

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.

@llogiq
Copy link
Contributor Author

llogiq commented Sep 10, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants