port=<value>

Specify the port that the profiler agent listens on for communication with the Profiler.

By default, the port is chosen automatically: if port 10001 is free, it is used; otherwise, if port 10002 is free, it is used etc.; if no port in the range 10001..10010 is free, an arbitrary free port is used.

listen=<ip>:<port>

Same as port but this binds agent socket to a particular IP only

Allow only local connections to profiled application

dir=<directory for snapshots>

Specify custom snapshot directory for the particular profiled application

delay=<milliseconds>

Postpone start of telemetry collection. This option is mostly intended to prevent startup issues of some J2EE servers.

By default, light-weight telemetry is collected right from the start of the profiled application.

The telemetry is collected via so called platform MBeans ("managed beans") - the components for monitoring and managing the JVM. Some J2EE servers install their own implementations of standard MBeans. In earliest stages of the server startup the MBeans can not be functional because they depend on other components of the server (such as custom logging) which have not initialized so far. Accessing such MBeans in earliest stages can cause the server startup failure (e.g. with ClassNotFoundException).

The "delay" option ensures that all MBeans are completely initialized before they are first accessed, by postponing the start of collecting the telemetry.

The J2EE integration wizard by default uses "delay=10000" to postpone the telemetry for 10 seconds. Although not all servers (and not all versions of particular server) suffer from the problem with MBeans, it is recommended to always use "delay" profiling a J2EE server to ensure that any J2EE server can successfully start. Furthermore, the telemetry of first few seconds of the server startup is unlikely of any interest for you, because the server's internals are being initialized during that time rather than your own application code.

If the 10 seconds delay is not enough in your particular case, try a bigger value.

The telemetry information is remembered inside the profiler agent. This allows to connect to profiled application on demand, being able to discover how the application has behaved in the past.

By default, the telemetry buffer is limited to store approximately 1 hour of recent telemetry data.

With the help of the telemetrylimit option you can customize the time period within which the telemetry data is being stored.

Do not use unnecessarily long buffers

Extending the telemetry buffer will allocate additional amount of memory in the profiled application's address space. That is especially important for 32-bit JVMs configured to use big heap (-Xmx) because total process memory is limited to 2-4 Gb (depends on OS) and JVM failure may happen if enough memory is not available outside the heap space.

Also, the longer the buffer, the more time it takes to retrieve the telemetry information from the profiler agent when you connect to a long running profiled application.

The limit is not exact

It is not guaranteed that data will be kept within exactly specified hours. hours is rather an approximation; the actual time may slightly (+/- 5 minutes) differ to ensure best performance.

Specify how often telemetry information is obtained.

By default, the period is 1 second (1000 milliseconds).

Note that setting smaller period can add overhead.

Probes: limit the number of rows to be stored by the profiler agent per table. Read more...

Specify the number of recently finished threads for which CPU sampling, tracing and monitor profiling results are kept (the default value is 50). Profiling results for the finished threads beyond this limit are merged to <Oldest finished threads> pseudo-thread node. The intention is to limit collected data size when profiling applications constantly creating new short living threads.

Always capture a memory snapshot on profiled application exit.

If this option is not specified, the memory snapshot will be captured on exit if object allocation recording is running at that moment.

Always capture a performance snapshot on profiled application exit.

If this option is not specified, the performance snapshot will be captured on exit if CPU sampling or tracing or monitor profiling is running at that moment.

This option is automatically added when the profiled application is started from the IDE.

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.

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 disabletracing.

Do not perform J2EE high level profiling. This option influences only CPU profiling started with sampling or tracing. Read more about CPU profiling modes.

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.

Do not perform per-class garbage object allocation recording. This option influences only allocation recording started alloceach and allocsizelimit.

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.

Automatically capture a memory snapshot when used heap memory reaches the threshold.

Periodically capture performance snapshots.

Periodically capture memory snapshots in the profiler's format (*.snapshot).

Periodically capture HPROF snapshots.

Do not collect thread stack and status information shown in Thread view as well as in other telemetry views. This information can be very useful because it allows you to connect to the profiled application on demand and discover how the application behaved in the past. In most cases, there is no significant overhead of collecting this information. However, it makes sense to disable it in production J2EE servers in order to ensure minimum profiling overhead. See also: Profiling overhead: how to reduce or avoid.

Do not collect exception telemetry. The exception telemetry helps discovering performance issues and logic errors. In most cases, there is no significant overhead of collecting this information. However, it makes sense to disable it in production J2EE servers in order to ensure minimum profiling overhead. See also: Profiling overhead: how to reduce or avoid.

Disable on OutOfMemoryError snapshots. Note that enabling on OutOfMemoryError snapshots adds absolutely no overhead. If OutOfMemoryError happens, memory snapshot is written to disk for further analysis. You may want to disable the snapshots in some very special situations, e.g. if you profile an application with a huge heap, for which capturing the snapshot may take significant resources (time and/or disk space), but do not plan to perform its memory analysis.

Specify probe class(es) to be registered on startup. Read more...

Specify where to find probe class(es) which are registered by class name. Read more...

Specify where to find probe class(es) which are registered by class name. Read more...

Enable strict probe validation: treat probe registration warnings as errors. Read more...

Register all built-in probes on startup (default behavior) Read more...

Register none of the built-in probes on startup Read more...

Do not register particular built-in probes on startup. Read more...

Specify the file with description of the triggers to be applied from startup.

If this option is not specified, the trigger description is read from <user home>/.yjp/config/.triggers, where user home corresponds to the account under which a profiled application is launched.

By default, that file does not exist, thus no triggers are applied.

Do not instrument bytecode with instructions needed for object allocation recording. See also: Profiling overhead: how to reduce or avoid.

Do not instrument bytecode with instructions needed for CPU tracing. Only CPU sampling will be available. See also: Profiling overhead: how to reduce or avoid.

Do not instrument bytecode with instructions needed for J2EE profiling. See also: Profiling overhead: how to reduce or avoid.

Disable several capabilities at once: disablealloc, disabletracing, disablej2ee, disableexceptiontelemetry, disablestacktelemetry, builtinprobes=none

Print brief description of startup options.