Re:JRE 8 needs more codecache than before
by user5994461 on Thursday September 15, 2016 @04:22PM
(#12509508)
Yes. The good approach when you're given a legacy java application with tons of flags is to removed ALL the optimizations flags for the heap and the GC.
Most of the settings found in legacy projects or on the internet are either obsolete or defaults in the latest version of the JVM.
The only mandatory heap flag is: "-Xms???M -Xmx???M" which set the heap size of the application to ??? megabytes.
Re:JRE 8 needs more codecache than before
by benzewdu on Friday September 16, 2016 @04:46PM
(#12517207)
Not even -Xms -Xmx, there's heuristics built in to appropriately size the gc spaces... http://hg.openjdk.java.net/jdk8/jdk8/hotspot/file/tip/src/sh...
Re:JRE 8 needs more codecache than before
by user5994461 on Saturday September 17, 2016 @04:06PM
(#12522200)
Right. Most applications don't need that.
It's only the server apps running 24/7 on fixed hardware that should have a defined memory usage.
Re:JRE 8 needs more codecache than before
by billsmithaustin on Thursday September 15, 2016 @12:51PM
(#12507711)
Yes, I think that approach would avoid propagating inappropriate or unnecessary settings.
After getting a baseline measurement of performance with JVM defaults, experiment with tuning a couple of settings, measure some more, make sure nothing breaks under load. Repeat until new JVM version seems stable/performs better/etc even under worst load and then upgrade all nodes to the latest and greatest?