![]() |
The information required to start a profiling run is called a session. Sessions are saved in the file {User home directory}/.jprofiler9/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
|
![]() |
The session settings dialog can be invoked from
|
![]() |
The session settings dialog is divided into 5 sections:
|
![]() |
If you change filter, profiling, trigger or probe settings for an active session,
the new settings
can be applied immediately if you profile a 1.6+ JRE.
Apart from telemetry data, all recorded data including the heap dump in the heap walker
will be
discarded in that case. When profiling settings are updated, a
bookmark will be added to views with a time-line, such
as the telemetry views. The application of the new profiling settings may take some
time,
especially if filter settings are changed and the method call recording type is set
to
dynamic instrumentation. In this case, changes in the instrumentation requires that
classes have to be retransformed to reflect the new filter settings.
If you profile a pre-1.6 JRE, you have to restart the session. View settings on the other hand, are always adjustable during a running session and are saved separately for each session. |