News for hackers. Stuff that matters.

A comment on Create your own Game Engine but don't use it. Parent comment

Re:Create your own Game Engine but don't use it by TeMPOraL on Wednesday July 12, 2017 @02:44PM (#14755308)
Some of the work done to work around GC feels similar to the work you'd do in C/C++ to work around memory fragmentation issues. Also, depending on the language/runtime, you might be able to influence the GC algorithm, or at least the frequency with which it runs. If you can e.g. run a GC every second for not longer than ~1 frame, then pauses won't be noticeable.
[ Parent | on HN ]
Re:Create your own Game Engine but don't use it by karmadog on Wednesday July 12, 2017 @05:14PM (#14756746)
A dropped frame is always noticable. What you can do is keep a budget for GC and then force-collect every frame.
[ Parent | on HN ]