Certain tunable parameters are sensitive to the size of compiled methods.
They need revisiting, since machines are larger than when the parameters
were last tuned (Tiger or before).
In particular, certain newer optimizations (bimorphic inlining) create larger
methods which in turn fall foul of the restrictively turned parameters.
Parameters which may need inflation include:
InlineSmallCode
MaxInlineSize
MaxTrivialSize
NodeCountInliningCutoff
MaxNodeLimit
InlineThrowMaxSize
MaxTrivialSize
FreqInlineSize
Vladimir reports that changes optimizing JVM98 run into InlineSmallCode limits below 2200.
They need revisiting, since machines are larger than when the parameters
were last tuned (Tiger or before).
In particular, certain newer optimizations (bimorphic inlining) create larger
methods which in turn fall foul of the restrictively turned parameters.
Parameters which may need inflation include:
InlineSmallCode
MaxInlineSize
MaxTrivialSize
NodeCountInliningCutoff
MaxNodeLimit
InlineThrowMaxSize
MaxTrivialSize
FreqInlineSize
Vladimir reports that changes optimizing JVM98 run into InlineSmallCode limits below 2200.
- relates to
-
JDK-6445664 Eliminate remaining performance penalty for using assert
-
- Open
-
-
JDK-8035809 Improve inlining of Class::cast method
-
- Closed
-
-
JDK-6565458 10x performance regression on x86 in micro test with Reflection.
-
- Open
-