Re: Optimizing for Java and Tomcat (x-posted) -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 11/20/13 3:10 PM, Dan Kimmel wrote:

"Optimize" is a loaded term. I don't know of any methods to optimize,
though I know a few tricks to make java (and Tomcat) run faster.

First, run java in its own storage pool. There's a couple ways to do
this. I create a separate subsystem and allocate a pool to it. I
allocate either a private pool or one of the *SHRPOOLxx's. . . .

Would anybody happen to have a recommendation on a tutorial for this?

The J9 jvm's beat hell of the classic except in rare circumstances.
On older versions of the OS, that's usually what's known as the "32
bit" jvm. On newer systems, there's 64-bit versions of some J9's
depending on Java version.

At the moment, we have Tomcat running in the JVM at
/QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit
on a V6R1 box. The CL we use to start Tomcat has that as its first choice, and failing to find it looks for (in this order):
/qopensys/QIBM/ProdData/JavaVM/jdk60/32bit
/qopensys/QIBM/ProdData/JavaVM/jdk626/64bit
/qopensys/QIBM/ProdData/JavaVM/jdk626/32bit
/qopensys/QIBM/ProdData/JavaVM/jdk70/64bit
/qopensys/QIBM/ProdData/JavaVM/jdk70/32bit
and takes the first one it finds. Should I change this to prefer 32-bit JVMs over 64-bit?

--
JHHL

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.