Session Startup Dialog

  Before a session is started, the session startup dialog is displayed. This dialog displays short summaries for the

of the profiled session as well as [Edit] buttons that lead to the corresponding sections of the session settings dialog.

When profiling, there is a general trade-off between profiling overhead and information depth. Most likely your personal requirements will change from profiling run to profiling run, so these settings are displayed every time before your application is started.

  For IDE integration users, this is the dialog where session settings can be accessed and modified. Session settings are persistent and are associated with the project name in the IDE.
  In the Startup And Exit section dialog you can choose a recording profile that should be set on startup. For many profiling use cases the startup phase of an application is not of interest. For large applications servers, you can save a lot of memory and speed up the startup phase by not recording any data from the beginning.

JProfiler provides a couple of default recording profiles. You can create new recording profiles or change existing ones by clicking on [Configure] next to the recording profile drop-down list.

When the JVM exits 3 different strategies are available:

  • Let the JVM exit and disconnect
    All profiling views will be unavailable after the JVM exits. This is the default setting.
  • Keep the VM alive for profiling
    JProfiler will prevent the JVM from exiting so that you can continue to work with profiling views. When you disconnect the profiling session, the JVM will be allowed to exit.
  • Save and immediately open a snapshot
    When the JVM exits, JProfiler will save a temporary snapshot and immediately open it in the same window. The "Session->Save" action will be enabled, so you can save the snapshot to a permanent location, if desired. When you close the window without saving the snapshot, the temporary snapshot will be discarded. This mode is especially suited for profiling test cases.

If you click on the "More" link next to the "Configure" button, additional options are shown for adjusting request tracking settings and disabling triggers. By default, triggers are enabled on startup. Triggers can also be enabled or disabled manually later on.

  The performance indicator is set according to the selected profiling settings and recording profile. Please note that this value is only approximate and that the filter settings influence overhead as well.
  When you click on [OK], the session will be started.