Re:Java 18 / JDK 18: General Availability
by kaba0 on Tuesday March 22, 2022 @12:50PM
(#30768440)
For a typical business app, I really don’t think there is all that much overhead. Java is very fast, virtual calls are basically free due to the JIT, and these apps usually don’t need that much cache coherency for issuing an SQL query for a request. It’s not decoding video.
[ Parent
| on HN ]
Re:Java 18 / JDK 18: General Availability
by vorpalhex on Tuesday March 22, 2022 @01:43PM
(#30769125)
If you think 512mb of base memory usage is "nothing" and you're ok with slow program start times, that's probably fine.
If you're like me and you sort of get sad when your program uses more than 64mb when idle because it feels wasteful, then yeah that overhead is pretty gnarly.
"But we have servers with hundreds of gigs of ram!" you might respond - and sure, we do, but having resources doesn't mean you have to use them. It is better to write small fast efficient programs than extravagant enterprise stuff.
What about the fact that Java is the most energy efficient managed language? Not constantly crunching through memory to choose which memory should be freed is efficiency, not laziness/bloat.
Sure, there are use cases where it is not a reasonable tradeoff, but for CRUD business apps, it is perfectly fine. Especially given that not all cores can be used uniformly.