Collecting thread data

Begin thread analysis by collecting thread analysis data for a profiling run.

Prerequisites:

• Agent Controller must be running on the machine on which you are collecting data. For information, refer to the installation guide.

• Create a profiling configuration. Read Getting started: Creating a profiling configuration for run-time problem determination.

To collect data:

1. In the Profiling tab (Overview subtab) of the Profile dialog box, select the Thread Analysis profiling set.

2. To modify settings in the profiling set, click the Edit button to display the Edit Profiling Set dialog box. You can do the following:
   • Disable data collection for the UML2 Object Interactions view. To do this, expand the Thread Information node and select the Thread Analysis entry. Remove the check for Collect UML2 Sequence Diagram object interaction data. Note that the UML2 Object Interactions view makes it possible to identify objects responsible for thread bottlenecks.

   • Collect data for boundary classes that are excluded by the filter set. To do this, expand the Time Analysis node. Check the checkbox for Execution Time Analysis. In the Execution Time Analysis page, check the checkbox for Collect boundary classes excluded by the filter set, and set the boundary class depth.

3. Optionally, specify a number of method invocations or an amount of time as the limit for data collection. This can speed up the data collection process.
   1. In the Profile dialog box, select the Profiling tab and the Limits subtab.

   2. Enter instructions for stopping profiling after a specific number of method invocations or after a specific amount of time.

4. Click Profile to start your application.

5. Exercise the parts of your application that are experiencing thread bottlenecks. You can now terminate your application.

 

Parent topic

Detecting thread bottlenecks

 

Related tasks

Identifying thread bottlenecks