luke warm methods?
ben.evans at db.com
Thu Apr 29 02:02:06 PDT 2010
hotspot-dev-bounces at openjdk.java.net wrote on 22/04/2010 00:42:28:
> We decay counters periodically since over time counters should only
> go up so maybe that's the problem. If you run with -XX:-
> UseCounterDecay it will turn it off but all the other flags that
> control it aren't available in product mode. This is certainly one
> of the pathologies of an invocation counter based system with
> relatively high thresholds.
Just so I'm clear, this doesn't affect the compiled status of methods,
What's being discussed here is that if an initial burst of activity
results in a method being called say 4096 times (vs a threshold of 10000),
then after 1 minute, then that method has had its invocation counter
reduced to 1024.
So the usual scenario whereby HotSpot reaches a steady state in terms of
compilation activity can be disrupted by a sudden flurry of activity on
rarely-used methods (which will be effectively cold due to the decay
process), which pushes the invocation counts of these methods above
compilation threshold. If these methods then go quiet again, then HS will
*not* deoptimize and drop these methods back to interpreted mode, even if
their invocation counters subsequently decay below threshold. Correct?
GFFX Auto Trading
Deutsche Bank, London
Office: +44 (0)20 7541 3953
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-dev