Considering making jemalloc (via https://github.com/alexcrichton/jemallocator …) explicitly opt-out via a feature flag in sled, so the default gets 300%+ better performance. Any #rustlang folks know of a good reason not to do this? My assumption is that 95% of rust users don't override the allocator
-
-
I agree on an aesthetic level, but one of the highest values of the project is "great performance with zero user tuning" and since rust no longer uses jemalloc by default it cuts performance significantly
-
i feel like this ought to wait for custom allocator APIs to be stable, so that you can use it within your library without affecting global program properties
End of conversation
New conversation -
-
-
Is it possible to check the allocator at runtime and warn? Potentially with a feature flag to mute the warning?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.