Thanks for the response. It does seem to be related to the amount of data promoted, but that isn't the only factor at play, Here's a plot of the amount of data promoted per ParNew above the ParNew duration for a two hour window:
[image: Inline image 2] As you can see long ParNews imply a large promotion but not the reverse. What second factor might be involved? We're looking into what is different in the application at this time. The majority of the heap and hence promoted data is part of a Berkeley DB Java Edition database cache. The database cache holds all of the data and is otherwise stable. There are other activities like database checkpointing and cleaning that happen in the background, but those are going on all of the time. Are there any more JVM options that we could shed light on what's happening during the ParNew collections? David
_______________________________________________ hotspot-gc-use mailing list hotspot-gc-use@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
