RFR (S): 8148940: java/lang/ref/FinalizeOverride.java can time out due to frequent safepointing
zoltan.majo at oracle.com
Fri Feb 26 11:09:18 UTC 2016
On 02/26/2016 11:50 AM, Aleksey Shipilev wrote:
> On 02/26/2016 01:47 PM, Tobias Hartmann wrote:
>> I still wonder why we then do 2x compilations with ISC enabled? Do
>> the bootstrapped invokedynamic call sites invoke that many methods
>> compared to the baseline without ISC?
> I think that's because current ISC not only prompts the compilation of
> java.lang.invoke infra, but also spins up an anonymous class that holds
> the concat stub (to be switched off in a few weeks), which would also
> get compiled when hot.
It would be interesting to know what the contribution (1) of the
initialization of the java.lang.invoke infrastructure and (2) of the
concat stub is.
> Anyhow, that's a trigger, and not the underlying issue. The underlying
> issue is DoSing the JVM through System.gc/runFinalization busyloop.
Yes, I agree that this is a test problem that ISC triggered.
But I think it is important to figure out what is the cost of the
initialization of the java.lang.invoke infrastructure and of the ISC
infrastructure. If these initializations happen at (or closely after) VM
startup, they can potentially increase VM startup time.
So I filed a bug to investigate this problem:
More information about the hotspot-compiler-dev