Hacker News new | ask | show | jobs
by cetico 2842 days ago
IMHE, generations are a nightmare to operate for high performance servers at scale because you have to balance the sizes of those heaps manually and it can change abruptly with code changes or workload fluctuation.

Go allocations are indeed costlier but the performance critical sections of applications can be profiled and optimized accordingly to remove allocations.

I'd rather have Go's amazing low GC latency and slightly higher allocation costs vs the operational nightmare from HotSpot.

Automatic management of generations has never fully worked in Java. Every new JDK version just adds more knobs. Sounds like you have a different experience?