Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Profiling with TPTP - plug-in development

Revision as of 09:26, 8 October 2008 by Ewchan.ca.ibm.com (Talk | contribs) (Memory Analysis : Identify a memory leak)

Overview

  • This page shows how to quick start a profiling session on a plug-in project. TPTP must be installed on an Eclipse workbench, for more information on installation, please read Install TPTP with Update Manager.

Profile a plug-in project

  • 1. Select a plug-in project and select Profile As > Eclipse Application.
Pluginscreen1.jpg
  • 2. In the profile configuration dialog, under Monitor tab, select Java Profiling agent and select Edit Options.
Pluginscreen2.jpg
  • 3. In Filter page, add a new filter.
Pluginscreen3.jpg
  • 4. Input a new filter that includes your plug-in packages. eg.,
sample.myplugin* * INCLUDE
Pluginscreen4.jpg
  • 5. Click Finish to apply filter.
Pluginscreen5.jpg
  • 6. Click OK to start profile session.
Pluginscreen6.jpg
  • 7. Select Yes to switch to profiling perspective upon request.
Pluginscreen7.jpg
  • 8. Profiling resources (process, agent, and analysis type) are created in Profiling Monitor view.
Pluginscreen8.jpg
  • 9. Interact with your Run-time workbench for profiling agent to collect profiling data.
  • 10.In the development workbench, double-click on an analysis type to open a profiling view to show profiling data collected.
Pluginscreen9.jpg


  • 11.In profiling table view, select any column header to sort the table.
Pluginscreen10.jpg

Execution Analysis : Identify a bottleneck

TPTP provides tools and views to help identify execution bottleneck problem, please take a look at Execution Analysis for more information.

Memory Analysis : Identify a memory leak

TPTP provides tools and views to help identify potential memory problem in an application, please take a look at Memory Analysis for more information.

Thread Analysis : Identify threading problem

Thread or job problem can be identify with the help of Thread Analysis. Thread Analysis can be enabled in the launch configuration by selecting Thread Analysis type of a Java profiler.

Sanp29.jpg

If contention information is required, enable the Contention Analysis option in the Edit Option detail of the analysis type.

Sanp30.jpg

Double-clicking on the profile agent opens the Thread Statistics view which shows thread related information of an application under profiled.

Sanp31.jpg

Selecting any thread instance in the table and click Show Call Stack button opens Call Stack view that shows stack information of the selected thread.

Sanp32.jpg

More detail information can be acquired by switching to the Monitor Statistics tab which shows information of class monitored in each thread.

Sanp33.jpg

The Threads Visualizer tab shows a graphical representation of the thread analysis, Legend is available in the Legend button.

Sanp35.jpg

Mouse over any thread in the view shows details about the selection.

Sanp36.jpg

Back to the top