-
Notifications
You must be signed in to change notification settings - Fork 108
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
Q: How does the performance compare with mimalloc? #273
Comments
@sirinath do you have a feature in mind? |
It seems like |
I don't believe mimalloc is unmaintained. @daanx is out of office at the moment so I can't double check with him. But generally he does a big push on mimalloc support every few months. |
mimalloc is the default allocator used in Koka. So it is being maintained, I suppose. |
Could you plant pareto principles from scalloc? In my benchmarks, it even outperforms jemalloc on skylake. |
@osevan it is a while since I read the scalloc paper. If you could say a bit more about your suggestion that would be helpful. Also, could you share the benchmarks? Or even add them to mimalloc-bench? Seeing benchmarks can often help understand the weaknesses of certain aspects of the design. |
My benchmarks are old and i did that after scalloc appear in world. And i cant find my Benchmarks :-( Btw i was in my tests fastest one on skylake with lowest latancy. I tested several benches with jemalloc tcmalloc rpmalloc and lockless lalloc and in case where lowest latency possible was scalloc thread creation bench , the best. I think you can try to fix compile errors with latest gcc and clang and we can test this again. |
Is this one daanx/mimalloc-bench#90 fixed in mimalloc-bench? |
The text was updated successfully, but these errors were encountered: