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 10:43, 16 October 2008 by Ewchan.ca.ibm.com (Talk | contribs) (Profile a plug-in project)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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.
  • This page is provided as part of the TPTP profiling initiative to improve the usability of the TPTP profiler. If you are a plug-in developer and would like to participate and help improve the TPTP profiler, please contact Eugene Chan. The profiling initiative pilot is currently targeted to close on December 2, 2008.
  • Note on Agent Controller (AC) requirement: An Integrated Agent Controller (IAC) is shipped within Eclipse TPTP since TPTP version 4.4.2 and it is NO longer required to have a separate installation of agent controller for local profiling. Standalone Agent Controller is only needed for remote profiling. If you have any agent controller process running locally, you can simply stop or terminate the AC process and let the IAC start and stop on demand for your profiling session. Make sure also no dangling Java process running on the same machine that was started by the previous AC session.



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 the profile session with default Execution Time Analysis. For other analysis type, please see sections below for more information.
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

TPTP provides tools and views to analysis threading problem in an application, please take a look at Thread Analysis for more information.


Performance Overhead

The Performance overhead of a profile session mainly depends on the profile configuration which includes configuration of profile filter and profile options. Please see Profiling configuration for detail about how to control the amount of profiling data hence the overhead in a session.


Hints and Tips

See TPTP FAQ page for detail on hints and tips for a profiling session.

Known issues

Refer to TPTP FAQ page for known issues and workarounds.



Back to TPTP wiki page

Back to the top