[15:16:41] Michael Kopp: In my last post I explained what a major Garbage Collection is. While a major Collection certainly has a negative impact on performance it is not the only thing that we need to watch out for. And in case of the CMS we might not always be able to distinguish between major and minor GC. So before we start tuning the garbage collector we first need to know what we want to tune for. From a high level there are two main tuning goals.
Execution Time vs. Throughput

The first thing we need to clarify if we want to minimize the time the application needs to respond to a request or if we want to maximize the throughput. As with every other optimization these are competing goals and we can only fully satisfy one of them. If we want to minimize response time we care about the impact a GC has on the response time first and on resource usage second. If we optimize for throughput we don’t care about the impact on a single transaction. That gives us two main things to monitor and tune for...

Read the rest of the article where I explain how to identify the impact on garbage collection and how to best avoid it.

Very good post. Made me realize I was totally wrong about this issue. I figure that one learns something new everyday. Mrs Right learned her lesson! Nice, informative website by the way.
<strong><a title="nba jerseys" href="http://www.mynfljerseysonline.com/nfl-jerseys-san-diego-chargers-jersey-c-139_169.html">chargers jersey</a> </strong>