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.
Difference between revisions of "PTP/designs/perf tools framework"
(→Performance Tools Framework) |
(→Performance Tools Framework) |
||
| Line 7: | Line 7: | ||
existing performance tools with Eclipse. | existing performance tools with Eclipse. | ||
| − | Goal: generalize and extend performance tools | + | Goal: create the eclipse "plumbing" to ease the integration of existing performance tools, both internal (implemented within Eclipse) and external; |
| + | generalize and extend existing performance tools' integration with PTP | ||
Integration points are envisioned to include: | Integration points are envisioned to include: | ||
Revision as of 09:51, 6 November 2007
Performance Tools Framework
An implementation of an initial performance extension for ptp has been done for TAU, and is available in the PTP CVS repository, under org.eclipse.ptp/tools/tau.
Currently under development (July '07) is a generalized performance framework to assist tool developers in porting their tools to Eclipse, or easily integrating existing performance tools with Eclipse.
Goal: create the eclipse "plumbing" to ease the integration of existing performance tools, both internal (implemented within Eclipse) and external; generalize and extend existing performance tools' integration with PTP
Integration points are envisioned to include:
- Instrumentation
- automatic vs. manual (including user-assisted e.g. via eclipse actions)
- selective implies some filters of types of instrumentation to add
- Build, which may or may not be transparent to user
- Launch with instrumentation
- Management of profile/trace data
- Visualization / Analysis of profile/trace data
Note: Performance tools have also been classified in three phases:
- Instrumentation
- Measurement (which would include build and launch, measurement during the run)
- Analysis (which could include management of data as well as analysis including visualization)
See also Performance Analysis Use Cases at [1]
To start with I (Beth Tibbitts) am prototyping some eclipse tools to assist users in adding performance
instrumentation lines to source code. So far about 90% of the code is in a generic plug-in to which
the user/client writes an extension plug-in that uses that and requires very little code to implement.
Next I will work on instrumentation that doesn't modify the user's source code at all,
a "transparent" instrumentation that e.g. instruments a copy of the source code then builds.
Others are working on other areas, but I won't speak for them at this point. As we firm up these areas and extension points, we'll publish more detailed information here. Stay tuned. (BRT 8/18/08)