3 ms·
It absolutely doesn't need any memory tuning whatsoever. People just read 2 decades old blog posts and apply whatever random flag they see. For 90% of workflow
by gf000 1mo ago
It absolutely doesn't need any memory tuning whatsoever. People just read 2 decades old blog posts and apply whatever random flag they see.
For 90% of workflows you don't add any command line arguments, for the remaining 10% you may specify a heap size. That's all.
- eerikkivistik 1mo agoPerhaps you work on simple CRUD applications? In my experience the 90/10 are reversed.
- gf000 1mo agoWhat do you need it for? Which version of the JVM?
- eerikkivistik 25d agoSure, a few examples that happen with modern JVMs (even 25). Essentially anything addressing a large amount of memory (think > 100gb). This can be databases, streaming solutions and so on, where you start tuning the GC just to have a smooth experience. Then there is the case of memory fragmentation of the heap, so you might want to switch out your GC. What else, basically any system that uses a lot of temporary memory is borked, because Java has a nasty habit of not returning unused heap to the OS by default. All in all, my point is, if you are doing anything that actually utilizes the hardware near its limits you will be tuning by quite a bit.
- gf000 25d ago> All in all, my point is, if you are doing anything that actually utilizes the hardware near its limits you will be tuning by quite a bit. What do you think happens in case of literally any other platform/programming language when you go near the limit? You are just either forced to change code, or.. well just put up your hand in the air, I guess and maybe buy better hardware?
- eerikkivistik 23d agoAs far as I can tell we are in violent agreement. When you do complicated things you have to tune, when you don't you don't.