Download Tuning Tips for JAVA GUI on Unix

Tuning Tips for JAVA GUI on Unix
There following are some tips for tuning up the performance of the TNG Java
GUI on DEC tru64 platform. They are applicable to other UNIX platforms.
1. Specify a larger heap using –Xms##m for starting value and
-Xmx##m for the maximum value. In TNG2.2, it could be changed in
w2startup script. In TNG2.4, it could be changed in the w2_env script.
Both files can be found under $CAIGLBL0000/wv/scripts directory. Search
for the following statement:
JAVA_ca="$JAVA_ca -classpath $CLASSPATH"
And then add the values:
JAVA_ca="$JAVA_ca –classpath –Xms##m -Xmx##m
$CLASSPATH"
Values between 128-512 seems to work the best.
2. We tested various values for “msg_tql” kernel parameter. 4096 seems to
work the best. The default value set by Java GUI installation is 1024.
The ipc subsystem attribute, msg_tql, specifies the maximum number of
messages that can be on a System V message queue; that is, the total
number of messages that can be outstanding in the system.
Performance Benefit and Tradeoff
Increasing the value of the msg_tql attribute may improve the performance
of applications that benefit from increasing the number of outstanding
messages to a value that is larger than the default value. However,
increasing the value of this attribute will consume memory.
You cannot modify the msg_tql attribute without rebooting the system.
3. “shm_max” kernel parameter also takes effect. We adjusted this value
accordingly.
The ipc subsystem attribute shm_max specifies the maximum size of a
single System V shared memory region.
Performance Benefit and Tradeoff
Increasing the value of the shm_max attribute may improve the
performance of memory-intensive applications that can benefit from a
large System V shared memory region. However, increasing the value of
the shm_max attribute will increase the demand for memory.
You cannot modify the shm_max attribute without rebooting the system.
Recommended Values
The default value of the shm_max attribute is 4194304 bytes (512 pages).
4. JDK v1.2.2 has a version of fast JVM. JDK v1.3 has its JVM in beta. From
our testing results, JDK v1.2.2 with fast JVM works the best and it was
installed on all the machines.
5. The auto-poll time of the console log in Java GUI is another key factor to
the activity of other Java windows. The refresh of the Java console log
is the bottleneck of communication to the back end server. If the poll-time
is too short which means the console is frequently refreshing, it hangs all
other java windows that are opened at the same time. 120 second is the
optimal value and it should never be set below 30 second.
6. Appletviewer
If you have problems with the TNG Browser Interface using your web
browser, then you have another option, using the Applet Viewer provided
in the Java development kit (JDK).
CA provides a batch file for Windows and a script for UNIX, named "tngui."
This script will invoke the appletviewer program for you. To use this script,
simply log on to a machine where the TNG Browser Interface server
components are installed and enter:
tngui
This will execute appletviewer, launch the TNG Browser Interface and
connect to the machine to which you are logged on. If you have the server
components installed on multiple machines you can enter the URL of the
machine you wish to connect to.
For example:
tngui http://machine_name/tng/tngbib.html
If the computer you are using does not have the server components
installed on it, you can usually download and install a Java development
kit for it. Once you have done this, you can use the Java development kit's
Applet Viewer to access the TNG Browser Interface. To do this, enter:
appletviewer http://machine_name/tng/tngbib.html