NonStop Server for Java 7.0 Programmer's Reference

Collecting profile data
Profiling with —Xeprof
Table 17 Supported –Xeprof options
On NonStop Operating Systems, the time interval between the start and stop signals
must be more than five minutes. This is because the Java thread switching process is
time_slice
slow due to the nonpreemptive nature of the NonStop Operating System. As a result,
the asynchronous signals might be lost if they are posted to the NonStop Operating
System Java process at very short intervals.
This option is not supported on NonStop Operating Systems.times=quick|thorough
Profiling with zero preparation
This feature is supported on NSJ7.
Profiling with –agentlib:hprof
Table 18 (page 103) lists the supported –agentlib:hprof options.
Table 18 Supported -agentlib:hprof options
cpu=samples is not supported on NonStop Operating
Systems.
cpu=samples|times|old
Analyzing garbage collection data
NonStop Java does not support G1 collector, therefore information available for G1 collector in
this section is not applicable for NonStop Java.
Using visualizer functions
Using monitoring displays
Monitor memory and/or heap activity menu
Process resident memory
Not supported on NonStop system.
Process virtual memory
Not supported on NonStop system.
Data region resident memory
Not supported on NonStop system.
Data region virtual memory
Not supported on NonStop system.
Monitor JVM and/or system activity menu
System call rate
Not supported on NonStop system.
Analyzing garbage collection data 103