Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's the most predictable and has much less overhead than a moving collector.


Only when we forget about the impact of cycle collections, or domino effects stoping the world when there is a cascade of counters reaching zero.

The optimisatios needed to improve such scenarions, are akin to a poor man's tracing GC implementation.


I didn't forget. That's predictable. It happens when the application code does something, or stops doing something, as opposed to the moving collector just doing it at random times.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: