NonStop Server for Java 4.2 Programmer's Reference

You can send a SIGQUIT signal to the JVM by typing
$ kill -QUIT java-process-id
You might need to specify the dump exit option as DOE=n to avoid an automatically generated
dump.
❍
Alternatively, type a control key plus a backslash (Ctrl+\), which generates a SIGQUIT signal in
the OSS environment.
❍
Avoid using the default profiling option, heap=all, which produces both the dump profile and sites
profile, because this option skews the sites profile.
●
Profiling Techniques
When you run HPROF, consider these techniques for using options:
Do not use multiple profiling options together because each option affects performance. Using a single
option provides data closer to typical performance than multiple options.
●
Try profiling both CPU samples and CPU times; the results from each may differ.
cpu=samples
cpu=times
●
Change the sampling interval to adjust to longer or shorter program intervals. Use
period=ms
●
Try varying the trace resolution:
Change trace depth:
depth=levels
❍
Remove line numbers:
lineno=n
❍
Add threads:
thread=y
❍
●
To determine whether the program uses a complex multithreaded scheme, use the monitor option
monitor=y
An empty result list is good.
●
Using HPjmeter
You can use the HPjmeter for profiling your application.
On the NonStop server platform, HPjmeter allows you to view profiler data graphically. You can obtain
HPjmeter without charge from HP.
To use HPjmeter, the dump file must be an ASCII text file and must be produced by NonStop Server for Java 4
after a normal termination or exception termination. If your application terminates with a signal, NonStop
Server for Java 4 will not generate the dump file.
For more information about HPjmeter including links for an HPjmeter tour and downloading, see HPjmeter
Overview and Features (http://www.hpjmeter.com).