Comment by dazzawazza

Comment by dazzawazza 4 days ago

I've used jemalloc in every game engine I've written for years. It's just the thing to do. WAY faster on win32 than the default allocator. It's also nice to have the same allocator across all platforms.

I learned of it from it's integration in FreeBSD and never looked back.

jemalloc has help entertained a lot of people :)

Iwan-Zotow 4 days ago

windows def allocator is pos. Jemalloc rules

Reply View 4 replies

ahartmetz 4 days ago

>windows def allocator is pos
Wow, still? I remember allocator benchmarks from 10-15 years ago where there were some notable differences between allocators... and then Windows with like 20% the performance of everything else!

Reply View | 1 reply
- ComputerGuru 3 days ago
  
  It’s improved considerably since.
  
  Reply View | 0 replies
int_19h 4 days ago

> windows def allocator
Which one of them? These days it could mean HeapAlloc, or it could mean malloc from uCRT.

Reply View | 1 reply
- carey 4 days ago
  
  malloc in uCRT just calls HeapAlloc, though? You can see the code in ucrt\heap\malloc_base.cpp if you have the Windows SDK installed.
  Programs can opt in to the _segment_ heap in their manifest, but it’s not necessarily any faster.
  
  Reply View | 0 replies