Thursday Jul 24, 2008

64-bit GlassFish, howto, wiki

JavaPerformance logo

If you need to break the 2GB or 4GB heap maximum barrier for your GlassFish-powered application, you can move to a 64-bit JVM. The topic of 64-bit JVM was touched upon here when GlassFish v2 was released. What wasn't explained is what configuration steps it takes.

A recent thread on the GlassFish forum pointed out that this wasn't well documented or at least easily accessible. This FAQ entry on the Wiki tries to fix this. Once you're set with the 64-bit JVM, the GlassFish Performance and Tuning Guide can come handy.

Let us know when you feel important questions are not well documented on the GlassFish wiki FAQ or on the product documentation. You can either add it yourself to the wiki or send us a ping on the Forum. Thanks!

Tuesday Aug 21, 2007

GlassFish v2, 64-bit and default VM

Duke Performance

Here are a couple of things that change with GlassFish v2 which should trigger better out of the box performance:

•  GlassFish v2 supports 64-bit and thus can have a VM with terabytes of heap (see Performance Tuning Guide).

•  The GlassFish v2 configuration no longer has an explicit -client switch for better startup time in development mode. This means that Ergonomics will kick in to determine which is best, client or server VM. Read more here.

•  GlassFish v2 also supports Java 6. Performance benefits are almost immediate and free (no code change, no recompile or redeploy). The use of JSR 199 by the JSP compiler is one of the benefits. The SPECjAppServer number is another one.