add mimalloc#212
Conversation
300f7ff to
485b030
Compare
|
Why do we need this change? Do we have some data which demonstrates how this change is improving performances of our apps? |
Yes, it’s a memory allocator that’s better suited to our use case: long-running processes with frequent allocations, high concurrency, and a need for consistent latency. The default global allocator isn’t ideal here, as it tends to increase fragmentation and introduce global locking during allocations. I will run benchmarks and share the results here. |
e2cd179 to
fb6d404
Compare
|
Should we close this @Shourya742 ? Or at least putting it in draft? |
|
I don't remember now, why we stalled this PR? |
|
I don't remember exactly now, but it was not something we ever planned? Maybe it makes sense to run again the analysis after the improvements on hotpath described here? |
|
That might be the case, once the hotpath thingy is in. I will give the numbers another shot. |


This PR switches the binaries to use mimalloc instead of the default glibc allocator, which can exhibit higher fragmentation and contention under our workload.