> Hmm... if the allocator affects performance so much, then maybe the code simply uses the allocator too frequently? I'm not familiar with musl's allocator so

> Hmm... if the allocator affects performance so much, then maybe the code simply uses the allocator too frequently? I'm not familiar with musl's allocator so it's hard for me to say anything about it. However what is pretty common is that modern allocators use thread local allocators to avoid hammering global locks too much. Since Rust is very concurrent you don't need too many allocations to benefit from these optimizations.