3 ms·
> for how long the GC is going to kicks in. 1ms (max, average at 50us) And for the 'when' I'll add that the very concept of having a concurrent GC means you d
by BenoitP 6y ago
> for how long the GC is going to kicks in.
1ms (max, average at 50us)
And for the 'when' I'll add that the very concept of having a concurrent GC means you don't need to do a (potentially pausing) malloc right in the middle of what you're trying to do.
- monocasa 6y agoThe kind of people that care about GC pause times have their own allocators that are as cheap as jvm allocations and cheaper deallocation. They aren't poopooing GC's and then just calling regular malloc and free.
- Thaxll 6y agoEngines rely on smart allocator and memory pool, they usually allocate everything beforehand. You're not running malloc between two frames. Imagine a game like Battlefield if you were to allocate memory for each fired bullet.