== Quote from Jarrett Billingsley ([email protected])'s article > On Fri, Jun 5, 2009 at 9:03 AM, Robert > Clipsham<[email protected]> wrote: > > Jarrett Billingsley wrote: > >> > >> Wow, just.. wow. I can't believe you got it working :D Thanks so > >> much; I'm sure other people will find this useful as well! > >> > >> At long last, I was able to test it! And... amazingly, it was 50% > >> slower than the default malloc/free :\ I even compiled it with > >> optimization enabled. > >> > >> In disbelief, I tried it in my virtualized linux box with GCC as well, > >> and got a similar result, so it doesn't seem to be DMC's fault.. > >> > >> Hm. Maybe it's just supposed to be faster for multithreaded code. > > > > Maybe you could try one of the many other malloc replacements? I believe > > firefox switched to jemalloc, I have no real knowledge of this sort of th > ing > > though. A quick google seems to come up with quite a few "fast" > > replacements, including one from Google. > > > I'll give some of them a shot. Hopefully getting others to compile > with DMC won't be nearly as much of an adventure :P
Isn't a multithreaded allocator on the agenda at some point for druntime? If so, is this considered a high-priority thing that will likely get done soon (IMHO it should be b/c without it the new threading model will be almost useless due to poor scalability), or is it a back burner thing?
