This is such a weird take. Java's been everywhere in prod in the industry for decades from backends running millions of qps to HFT to game clients. IME, the mo

This is such a weird take. Java's been everywhere in prod in the industry for decades from backends running millions of qps to HFT to game clients. IME, the most common GC problems I see are: - incredibly basic settings are wrong, like the max heap size - the app was written with some very poor behavior, e.g. unreal amounts of allocation or tons of allocation thrashing in tenured heap. There aren't even a lot of GCs knobs to "manage" anymore compared to a decade ago [0]. Don't treat your GC as a black-box machine with infinitely available resources, and you'll be fine. 0) https://docs.oracle.com/en/java/javase/22/gctuning/ergonomics.html https://docs.oracle.com/en/java/javase/22/gctuning/ergonomic...