On this tab of the profiling settings dialog, you can adjust various profiling options which govern the detail of the collected profiling data and the execution speed of the profiled application.

• Time settings
  • CPU time measurement
    Select whether you want times shown in the CPU view section to be measured in
    • elapsed time
      With elapsed time selected, the clock time difference between method entry and method exit will be shown. Note that if the thread state selector is set to its standard setting (Runnable). Waiting, blocking and Net IO thread states are not included in the displayed times.
    • estimated CPU time
      With estimated CPU time selected, the CPU time used between method entry and method exit will be shown. On Windows and Mac OS the system supplies CPU times with a 10 ms resolution which are used to calculate the estimated CPU times. On Linux and Solaris the VM does not supply a CPU time and the estimated CPU times are roughly estimated by looking at the number of runnable threads.

• VM life cycle control
  • Keep VM alive
    Installs a security manager which intercepts your application's calls to System.exit() and executes them after JProfiler's GUI front end disconnects. This option allows you to profile code sections which are close to a forced termination of the virtual machine. Don't use this feature when you profile an application server which installs its own security manager. If you get security related exceptions when profiling your applications, try unchecking this option.

• Dynamic views
  • Start with all views frozen
    To disable dynamic updates in JProfiler's views, you can check Start with all dynamic views frozen. Click on the unfreeze button in the toolbar if you want to start dynamic data to be displayed or fetch data manually with the  fetch data button which is visible only in the frozen state.
  • Transmission periods
    Based on the varying degree of computing expenses required for the different views, the transmission periods for the dynamic views have been split into two separate settings:
    • Call stack trees and thread history
      This setting influences the update interval of the
      • CPU view section
      • allocation monitor
      • allocation hot spots view
      • thread history view
    • Tables and graphs
      This setting influences the update interval of the
      • class monitor
      • VM telemetry view section