Quoting Bengt from earlier in this conversation:
"As for just doing a System.gc() to force a GC I think you can rely on that
System.gc() does a full GC in Hotspot unless someone sets
-XX:+DisableExplicitGC on the command line. Considering that you are relying on
Hotspot specifc names for pools
On 30.10.2013 17:30, Mandy Chung wrote:
On 10/30/2013 4:23 AM, Jaroslav Bachorik wrote:
Ok. I've added a big object and an initial call to System.gc(). But
I'm leaving the calls to System.gc() right before checking the pools
as well - just to be sure.
http://cr.openjdk.java.net/~jbachorik/8020
On 10/30/2013 4:23 AM, Jaroslav Bachorik wrote:
Ok. I've added a big object and an initial call to System.gc(). But
I'm leaving the calls to System.gc() right before checking the pools
as well - just to be sure.
http://cr.openjdk.java.net/~jbachorik/8020467/webrev.04
The update looks okay
On 24.10.2013 21:33, Mandy Chung wrote:
On 10/24/2013 7:01 AM, Jaroslav Bachorik wrote:
Hi Mandy,
On 24.10.2013 01:02, Mandy Chung wrote:
On 10/23/2013 7:32 AM, Jaroslav Bachorik wrote:
I've updated the patch. The GC is called even before the first attempt
to get the pool memory usage and S
