Determining optimal JDK memory config, faster

If you are like me, stuck with Java 5 for one reason or the other, you may be having difficulty determining how much heap to allocate to a process, and whether the ratio of young generation space should be different from default. A shortcut can be taken if your primary goal is maximum throughput. We know about HotSpot ergonomics, but with Java 5 it takes too long for it to work its magic. HotSpot in Java 6, on the other hand, usually has the optimal parameters figured out in a matter of hours. This makes it possible to increase turnaround of load tests and zero in on optimal settings very fast.