What are the startup options?
The startup options allow to customize some aspects of profiling. These options can be configured when you start the profiled application.
When should I specify the startup options?
In most cases, you do not have to specify any of these options, because default behavior suits fine in most cases.
How can I specify the startup options?
These options can be configured when you start the profiled application:
- from the IDE plug-in UI, if you start the profiled application from IDE
- with the help of agent command line parameter.
The options are comma-separated if you specify more than one option.
Description of the startup options
|
Main options These options can be switched on startup only, i.e. corresponding behavior cannot be altered during runtime. |
|
port=<value>
|
Specify the port that the profiler agent listens on for communication with the Profiler. |
listen=<ip>:<port>
|
Same as ' |
onlylocal |
Allow only local connections to profiled application |
dir=<directory for snapshots>
|
Specify the directory where snapshots are created. By default, |
onexit=memory |
Always capture a memory snapshot on exit. CPU snapshot will be captured automatically if CPU profiling is enabled when the profiled application exits. |
onexit=snapshot |
Capture recorded data (telemetry, and if recorded CPU and monitors profiling results) on exit. This option is automatically used when the profiled application is started from the IDE. |
quiet |
Suppress diagnostics messages that the profiler agent prints to the console. |
|
Turn on profiling modes right from the start Note that you do not have to perform measuring right from the start. Instead, in many cases it's better to start or stop measuring at a later moment - from the UI or by using the Profiler API. |
|
sampling |
Launch Java application with CPU sampling turned on. Note that you do not have to profile CPU right from the start; instead, in many cases it's better to start or stop measuring at a later moment - from the UI or by using the Profiler API. |
tracing |
Launch Java application with CPU tracing turned on. Note that you do not have to profile CPU right from the start; instead, in many cases it's better to start or stop measuring at a later moment - from the UI or by using the Profiler API. This option cannot be used in combination with 'disablecounts'. |
noj2ee |
Do not perform J2EE high level profiling. This option influences only CPU profiling started with 'sampling' or 'tracing'. Read more about CPU profiling modes. |
alloc |
Launch Java application with object allocation recording started. All objects will be recorded. Note that you do not have to record allocations right from the start; instead, you can start or stop recording later from the Profiler or using Profiler API. This option cannot be used in combination with 'disablealloc'. |
alloceach=<N> |
Launch Java application with object allocation recording started and record each N-th allocation. This option can be used in combination with 'allocsizelimit'. This option cannot be used in combination with 'disablealloc'. Note that you do not have to record allocations right from the start; instead, you can start or stop recording later from the Profiler or using Profiler API. |
allocsizelimit=<B> |
Launch Java application with object allocation recording started and record allocation of objects with size bigger or equal B bytes. This option can be used in combination with 'alloceach'. This option cannot be used in combination with 'disablealloc'. Note that you do not have to record allocations right from the start; instead, you can start or stop recording later from the Profiler or using Profiler API. |
monitors |
(Java 5 and newer) Launch Java application with started monitor profiling. Note that you do not have to profile monitor usage right from the start; instead, you can start or stop recording later from the Profiler or using Profiler API. |
usedmem=<percent> |
Automatically capture a memory snapshot when used heap memory
reaches the threshold. |
|
Optimization options Reduce profiling overhead by disabling some profiling capabilities. See Profiling overhead: how to reduce or avoid. These options can be switched on startup only, i.e. corresponding behavior cannot be altered during runtime. |
|
disablealloc |
(Java 5 and newer) Do not instrument bytecode with instructions needed for object allocation recording. See Profiling overhead: how to reduce or avoid. |
disablecounts |
(Java 5 and newer) Do not instrument bytecode with instructions needed for CPU tracing. Only CPU sampling will be available. See Profiling overhead: how to reduce or avoid. |
disablej2ee |
(Java 5 and newer) Do not instrument bytecode with instructions needed for J2EE profiling. See Profiling overhead: how to reduce or avoid. |
|
Miscellaneous |
|
help |
Print a short description of agent parameters. |