## Session Startup Dialog |

| Before a session is started, the session startup dialog is displayed. This dialog displays short summaries for the Filter settings Profiling settings Trigger settings 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` section dialog you can choose whether recording of CPU or allocation data should be started immediately. 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 allocations from the beginning. Record CPU data on startup Both the invocations view and the hot spots view will display data immediately. Record allocations on startup The recorded objects view will display data immediately. Enable triggers on startup By default, this option is selected. If you deselect this check box, triggers will not be enabled when the JVM is started for profiling. You can enable triggers manually later on. In addition, request tracking settings can be adjusted in the startup dialog.

| The performance indicators are set according to the selected profiling settings. Please note that these values are only approximate and the the filter settings influence overhead as well.

| When you click on [OK], the session will be started.