Sessions Overview
-
The information required to start a profiling run is called a session.
Sessions are saved in the file {User home directory}/.jprofiler5/config.xml
and can be easily migrated to a different computer by importing this file in the
setup wizard. When upgrading JProfiler, your settings
of older installations are imported automatically.
-
Sessions are created
Sessions are edited, deleted and opened
-
The session settings dialog can be invoked from
-
The session settings dialog is divided into 4 sections:
-
Application settings
The application settings section
collects all information that is required to start your application with profiling enabled or to
connect to a running JVM that has already been started with profiling enabled.
If you use an IDE integration, this information
will be provided by the IDE.
-
Filter settings
In the filter settings section, you
define which classes should be considered when recording call-stack information.
Defining appropriate filters will help you to reduce data overload and minimizing CPU profiling
overhead. By default, JProfiler adds an exclusion list
-
Profiling settings
In the profiling settings section you
can configure the way your application is profiled and change the focus of a profiling run toward
performance or accuracy, CPU or memory profiling.
-
Trigger settings
In the trigger settings section you can optionally
define a list of triggers. With triggers, you can tell the profiling agent to execute specific actions
when certain events occur in the JVM. The actions are also executed during
offline profiling.
-
To apply changes in the session settings to a live session, you have to restart the session.
View settings on the other hand, are adjustable during a running session and are saved
separately for each session.