On Thu, Feb 10, 2011 at 9:17 AM, Huy Le <hu...@springpartners.com> wrote: > Yes, we had setting at 75 but JVM did not have enough time to do GC, so it > abort GC'ing. We lowered it to 50, but still had issue, so we lowered it > again to 35.
If you lower CMSInitiatingOccupancyFraction below the size of your typical working set, the only thing you will do is burn a core's worth of CPU on constant GC, which is probably not accompanied by an improvement in overall system performance. ;D =Rob
