Code cache

[Eric Caspole]

Hi Alex,
You can try -XX:+UseCodeCacheFlushing where the JVM will selectively  
age out some compiled code and free up code cache space. This is not  
on by default in JDK 6 as far as I know.

What is your application doing such that it frequently hits this  
problem?

Regards,
Eric


On Apr 12, 2012, at 3:15 PM, Alex Aisinzon wrote:

> Any feedback on this?
>
>
>
> Best
>
>
>
> Alex A
>
>
>
> From: Alex Aisinzon
> Sent: Monday, April 09, 2012 11:38 AM
> To: 'hotspot-gc-use at openjdk.java.net'
> Subject: Code cache
>
>
>
> I ran performance tests on one of our apps and saw the following  
> error message in the GC logs:
>
> Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full.  
> Compiler has been disabled.
>
> Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code  
> cache size using -XX:ReservedCodeCacheSize=
>
>
>
> I scaled up the code cache to 512MB (- 
> XX:ReservedCodeCacheSize=512m) and markedly improved performance/ 
> scalability.
>
>
>
> I have a few questions:
>
> ·         Is there a logging option that shows how much of the code  
> cache is really used so that I find the right cache size without  
> oversizing it?
>
> ·         What factors play into the code cache utilization? I  
> would guess that the amount of code to compile is the dominant  
> factor. Are there other factors like load: I would guess that some  
> entries in the cache may get invalidated if not used much and load  
> could be a factor in this.
>
>
>
> I was running on Sun JVM 1.6 update 30 64 bit on x86-64.
>
>
>
> Best
>
>
>
> Alex A
>
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use