When you start a profiling session, you first select and configure the profiling task. You choose the profiling task according to the type of profiling results you want to obtain from the session.
Each profiling task has default settings that are sufficient in most situations. You can configure the basic settings of each profiling task to modify the profiling results that are returned. For greater control, you can also modify the advanced settings for the task by creating a custom configuration of the task.
The following table describes the profiling tasks and the profiling results obtained from running the task.
Profiling Task | Results |
---|---|
Monitor Application | Choose this to obtain high-level information about properties of the target JVM, including thread activity and memory allocations. |
Analyze CPU Performance | Choose this to obtain detailed data on application performance, including the time to execute methods and the number of times the method is invoked. |
Analyze Memory Usage | Choose this to obtain detailed data on object allocation and garbage collection. |
Each time you start or modify a profiling session, you first select a profiling task in the Select Profiling Task dialog box.
Alternatively, choose Profile > Attach Profiler or Profile > Profile Other > Profile Project "projectname" from the main menu.
The IDE supports using a load generator to replay previously saved load testing scripts. By using a load testing script, you can simulate a heavy load on your server or application in order to achieve more accurate results when testing application performance.
The IDE supports the Apache JMeter load testing tool. If you have an Apache JMeter load testing script, you can load the script when profiling an application. To load the script, select the LoadGenerator Script checkbox in the Select Profiling Task dialog box and choosing the script in the drop-down menu.
Notes: