Comment by winrid 3 months ago It's the most predictable and has much less overhead than a moving collector. 2 comments winrid Reply pjmlp 3 months ago 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. winrid 3 months ago 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.
pjmlp 3 months ago 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. winrid 3 months ago 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.
winrid 3 months ago 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.
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.