Coming from a gaming background i actually prefer simpler incremental GCs where i can finely control the step size. This would be my ideal GC: http://wiki.luajit.org/New-Garbage-Collector … . Being non-moving also allows easier integration with other languages.
-
-
-
Would you take a 10x hit in allocation performance in order to be non-moving? Because that's what it takes. Allocation in HotSpot is like 5 instructions. That is not something one should easily give up.
- 1 more reply
New conversation -
-
-
Scalar replacement is still worth it, even with a very good generational GC. It saves you the ~five instructions of allocations, minor collect runs less often, plus all the loads and stores to the object can be removed too.
-
(I agree that you should totally focus on a good GC first, if you don't have one. Also, the trade-off becomes a bit different again is your numbers are tagged instead of boxed)
End of conversation
New conversation -
-
-
@pypyproject Python implementation for one has incremental, generational and moving GC. But at the same time for hot functions their tracing JIT can do escape analysis and remove allocations. So I guess you can do both.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.