RFR: 8234863: Increase default value of MaxInlineLevel

Liu Xin navy.xliu at gmail.com
Mon Dec 9 05:19:19 UTC 2019


hi, Claes,
Glad to know that bigger scope for optimizations can offset the bigger
methods. Thank you for the clarification.

thanks
--lx


On Sun, Dec 8, 2019 at 4:19 PM Claes Redestad <claes.redestad at oracle.com>
wrote:

> Hi lx,
>
> On 2019-12-09 00:23, Liu Xin wrote:
> > Hi, Claes,
> >
> > If you increase MaxInlineLevel from 9 to 15, don't you need adjust
> > initial and maximal size of CodeCache?
>
> Not necessarily: yes, more aggressive inlining may lead to larger
> nmethods and less sharing overall, which *could* mean we need more code
> cache space over time. But it may also mean more aggressive dead code
> elimination, which can mean a net reduction in code cache utilization
> for some applications.
>
> For the applications and benchmarks we've tested, code cache utilization
> is largely the same. And while we can't rule out that some applications
> may see regressions, data strongly suggests a more aggressive setting
> will be better on average for most.
>
> > Could you elaborate 3x sub-benchmark? Is it java or scala?
>
> IIRC scala-kmeans was the sub-benchmark that saw the largest
> improvement.
>
> /Claes
>


More information about the hotspot-compiler-dev mailing list