3 ms·
It's all about the tiered compilation. Tons of unused but eagerly compiled code w/ C1 (the dumb and fast compiler) that never reached the proper C2. The issue
by xxs 10y ago
It's all about the tiered compilation. Tons of unused but eagerly compiled code w/ C1 (the dumb and fast compiler) that never reached the proper C2.
The issue has been three since 6.0.23 when the -XX:+TieredCompilation defaulted to true. (hmm, or was it 6.0.25?)
I'd say nothing really new.
If you run a server, just disable tired compilation altogether. It might cost few seconds slower startup but that's it.
- billsmithaustin 10y agoI believe TieredCompilation was disabled by default on Java 7u55: $ java -server -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version|grep TieredCompilation bool TieredCompilation = false {pd product} java version "1.7.0_55" Java(TM) SE Runtime Environment (build 1.7.0_55-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode) I would be interested in hearing from people with first-hand experience disabling TieredCompilation on Java 8 on production servers.