Profiling an application

The Profiling Tool offers powerful visualization features that enable you to pinpoint performance and memory usage problems within your applications. You can profile various types of  applications, including Java and Web applications, regardless of what application server you are running on. 

Note. The iSeries JVM requires the following options to generate method entry and exit events for method statistics:

      -Dos400.enbprfcol=1 -Djava.compiler=jitc

To profile an application, the Agent Controller must be installed and running on the host where the application under test resides.

Profile your Java, Web, or EJB applications from the Profiling and Logging perspective:

Selection box of perspectives showing selection of Profiling and Logging

Note: Profiling data can slow down your application. 

Workflow

The workflow for profiling is as follows:

  1. Set profiling preferences
  2. Set profiling filters
  3. Launch or attach a process
  4. Use the Profiling and Logging views to study the data being collected
  5. Save profiling data or resources if you expect to use them again

 

Related concepts
Overview of the Profiling Tool
Profiling resources
Profiling console view
Profiling monitor view
Sequence diagram views
Statistical views

Related tasks
Setting profiling preferences
Launching or attaching a Java process
Analyzing performance and memory usage - overview
Saving profiling data to an external file
Saving profiling resources
Importing profiling resources

Related reference
Time