Request for review (L): 7087838: JSR 292: add throttling logic for optimistic call site optimizations
forax at univ-mlv.fr
Sat Sep 17 02:33:10 PDT 2011
Hi Christian, hi all,
I understand that you need such kind of logic
but I think it's not compatible with the approach taken by Mark Roos
i.e flush all callsites if more than a predefined number of callsites
have installed an inlining cache.
A possible solution is to add a way in the API to know if a callsite
will trigger a deoptimization if the target changes.
On 09/16/2011 02:02 PM, Christian Thalinger wrote:
> [This change will be pushed after 7087357. So ignore the code removal in src/share/vm/classfile/javaClasses.cpp.]
> 7087838: JSR 292: add throttling logic for optimistic call site optimizations
> The optimistic optimization for MutableCallSite and VolatileCallSite
> invalidate compiled methods on every setTarget. This possibly results
> in a recompile. For ever-changing call sites this is a performance
> The fix is to add some throttling logic that prevents the optimistic
> optimization after a specified amount of invalidations per CallSite
> This change also moves the flush_dependents_on methods from Universe
> to CodeCache.
More information about the hotspot-compiler-dev