NonStop Server for Java Programmer's Reference (NSJ 4.0+)

toexit=full-method-name
Specifies to stop and generate a dump when this method exits.
Example
The following command shows using the fexit, upto, and only special options.
java -Xrunhprof:fexit=Test1.init,upto=Queue.cleanup,only=MyThread Test1
For more information, see the HPROF Profiler Agent described under Java Virtual Machine Profiler Interface
Machine Profiler Interface (JVMPI) (http://java.sun.com/j2se/1.4.1/docs/guide/jvmpi/jvmpi.html).
Tips
In the java command, specify no compiler:
-Djava.compiler=NONE
●
In Java native code (JNI), the CPU options also time native code where line-number information is not
available.
●
CPU time is not measured when process is blocked, for example, on a call to SQL.●
To dump profiling information before the program exits:
For sampling only, you can use a special option, such as upto and toexit.❍
Send a SIGQUIT signal to the Java VM 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 backwardslash (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
❍
●