Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Computadores - HP Integrity NonStop H-Series (16.73 mb)
Computadores - HP Integrity NonStop H-Series (957.56 kb)
Computadores - HP Integrity NonStop H-Series (881.66 kb)
Computadores - HP Integrity NonStop H-Series (965.62 kb)
Computadores - HP Integrity NonStop H-Series (676.93 kb)
Computadores - HP Integrity NonStop H-Series (393.72 kb)
Computadores - HP Integrity NonStop H-Series (776.57 kb)
Facilidade de uso
no -Xeprof option is specified, it is equivalent to:
-Xeprof:time_on=sigusr2,time_slice=sigusr2
There is no degradation of performance unless you actually start profiling by the specified signal.
times=quick|thorough
The quick value instructs the profiler to use the hardware Interval Timer register for time measurement. This value results
in faster profiling runs, but in extremely rare circumstances, it can produce bad data. This is the default value. If you ever
suspect that the profile data generated using the quick value is incorrect, re-run to see whether the results can be
replicated.
The thorough/strict value is the opposite of quick, and disables the use of the Interval Timer. The profiling runs will be
longer, and will provide timing data with the same (relatively poor) quality as the system calls used to measure the time.
The profiling intrusion and overhead will also increase. This is the default value.
Do not specify this option unless you know what you are doing. The collected profile data will almost certainly have less
accuracy than when collected using the quick value.
time_on=
Specifies the time in seconds between the application start and the time when the profile data collection will start. If no
time_on option is present, the data collection begins at the VM initialization.
time_on=sigusr1|sigusr2
Specifies which signal will cause profiling to begin (profile data collection). Ensure that the application or the VM may
already be using the sigusr signals for their own purposes; please check the documentation. Specifying a signal and a
timeout (see above) at the same time is possible by repeating the time_on option. Only one of the two signals can be
declared to use as the signal to start profiling. During the application's run, the specified signal can be delivered to the
Java™ process multiple times.
time_slice=
Specifies the time in seconds between the profiling start and the time when profiling will be terminated. When the
profiling is terminated, the profile data is written to a file. The application will continue running. If time_slice is not
specified, or if the application terminates before the specified time elapses but the profiling has started, the profile data
will be written out after the termination of the application.
time_slice=sigusr1|sigusr2
Specifies which signal will cause profiling termination and the profile data output. The signals for profiling start and
profiling termination can be the same. Specifying a signal and a timeout at the same time is possible by repeating the
time_slice option - termination of profiling occurs when the first qualifying event takes place. The application will
continue running. Only one of the two signals can be declared to use as the signal to terminate profiling. During the
application's run, the signal to terminate profiling can be delivered to the Java process multiple times. However, profiling
will only be terminated and a result file generated if profiling is active when the termination signal is delivered.
file=
The profile data will be written to the named file. If time_on=sig... has not been specified, the default is java
where
start profiling, several data files can be created, with names java
between the application start and the profiling start.
inlining=disable|enable
The compiler in the HotSpot VM optimizes Java applications by inlining frequently called methods. Execution of inlined
methods is not reported as "calls", since the actual calls have been eliminated. Instead, the time spent in an inlined method
...
Computadores - HP Integrity NonStop J-Series (85.74 kb)