Sessions overview
-
The information required to start a profiling run is called a session.
Sessions are saved in the file {User home directory}/.jprofiler3/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 settings for a session are collected in 2 steps:
-
application settings
The application settings dialog
collects all information that is required to start your application with profiling enabled.
This dialog is presented when you create a new session. From a running session it is available
through JProfiler's main menu via Edit->Application settings.
If you use an IDE integration, this information
will be provided by the IDE.
-
profiling settings
In the profiling settings dialog 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. 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.
Changes in the parameters of a session that are specified in the
application settings dialog or the
profiling settings dialog
are not made effective while that session is running. To change
session parameters, you need to detach JProfiler from your application and restart
the session. On the other hand, view parameters are adjustable during a
running session and are saved separately for each session.