News for hackers. Stuff that matters.

A comment on Mimalloc – A compact general-purpose allocator. Parent comment

Re:Mimalloc – A compact general-purpose allocator by bakery2k on Saturday June 22, 2019 @11:49AM (#20250206)
What if I'm writing code that's strictly single-threaded? Presumably malloc could be simpler and/or faster in this special case?

Is there a production-ready allocator that's optimized for single-threaded use?

[ Parent | on HN ]
Re:Mimalloc – A compact general-purpose allocator by imtringued on Sunday June 23, 2019 @05:27AM (#20254170)
It is already faster because there is no lock congestion.
[ Parent | on HN ]
Re:Mimalloc – A compact general-purpose allocator by gok on Saturday June 22, 2019 @12:08PM (#20250305)
It's very hard to not accidentally pull in a dependency that makes your code multithreaded.
[ Parent | on HN ]
Re:Mimalloc – A compact general-purpose allocator by 01100011 on Saturday June 22, 2019 @02:47PM (#20251070)
You guys could argue this all day and both be right. Depending on what type of system you're working on, you are either very likely to pull in a multithreaded dependency or you are not. Systems programming is different from game programming is different from web client programming is different from kernel development. In most of my career, I would have never accidentally pulled in a multithreaded dependency, but I could see how that could be easy to do in some cases.
[ Parent | on HN ]
Re:Mimalloc – A compact general-purpose allocator by rurban on Monday June 24, 2019 @07:48AM (#20262524)
For this use case a good copying collector would be best. Beats any malloc by miles.
[ Parent | on HN ]