inspecting the code cache
dmdabbs at gmail.com
Thu Mar 3 12:07:47 PST 2011
> -----Original Message-----
> From: hotspot-compiler-dev-bounces at openjdk.java.net [mailto:hotspot-
> compiler-dev-bounces at openjdk.java.net] On Behalf Of Tom Rodriguez
> Sent: Thursday, March 03, 2011 2:00 PM
> To: Charles K Pepperdine
> Cc: hotspot-compiler-dev at openjdk.java.net
> Subject: Re: inspecting the code cache
> On Mar 3, 2011, at 10:47 AM, Charles K Pepperdine wrote:
> > Hi,
> > Thanks for that information. I've been using PrintCompilation to
> watch what was going on. I've gotten a question from a client that
> claims that a method had seemingly been squeezed out of the cache. I'm
> not sure what would cause a method to be squeezed out but I guess it
> would have to be made not entrant before hand. But that got me
> interested in poking about to see what information one could squeeze
> out of the JVM wrt the code cache.
> Code will never get "squeezed" out in the current system. We generate
> code as needed and only get rid of it when it gets invalidated or if it
> references classes which get unloaded. If the code cache fills up you
> might not be able to compile something that needs code though.
> > TIA,
> > Kirk
Does -XX:+UseCodeCacheFlushing enable this clearing of invalidated code?
Or does that do something different?
More information about the hotspot-compiler-dev