logoalt Hacker News

The G1 Garbage Collector

68 points • by ejboy • last Tuesday at 4:29 AM • 21 comments • view on HN

Comments

pancakeguy • today at 6:50 PM

garbage collection will almost certainly be a relic of the past surprisingly soon. Fundamentally it exchanges efficiency for readability & developer experience, to things that do not matter when using AI to write code.

Fizzadar • today at 4:01 PM

I remember switching on G1GC for Elasticsearch back in 2014 and it was a total game changer for cluster stability (ES had plenty of other warts back then to counter the improvement). Cool to see it land as the default everywhere over a decade later.

➕ show 2 replies
ahmedfromtunis • today at 4:37 PM

I love that they also have learn.java and inside.java.

They should make get.java point to the download page. Oh and docs.java would be very cool!

Sid_Lmao • last Tuesday at 5:18 AM

Easy-to-miss detail: before JDK 27, the JVM only picked G1 with 2+ CPUs and ~1.8 GB of memory; otherwise, it silently used SerialGC. So a lot of 1- CPU Kubernetes pods have been on serial all along. Worth checking with -XX:+PrintCommandLineFlags before upgrading, since GC behaviour will change.

➕ show 1 reply
cyberax • today at 6:07 PM

And still no automatic heap sizing... Maybe next year?

_verandaguy • today at 3:08 PM

Tangential, but I really dislike that the `.java` gTLD was allowed to come about given it's also a reasonably popular file extension.

The `.zip` gTLD set a really bad precedent.

➕ show 1 reply