On 10/5/07, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Hi Wyatt,
It's great to see progress being made on this tool infrastructure. I have a few questions/comments:
1. I'd like to include the components that are providing generic performance tool support in the core PTP. This will require refactoring the generic parts into separate plugins and using extension points to provide the tool-specific functionality. Is this something you'd be willing to do?
The TAU specific functionality is being gradually shifted into the generic components. The goal is to eventually have most of TAU's functionality defined by its own tool XML file, rather than hard coded plugin components. I still need to look more closely at extension points for adding functionality that is tool specific. That is definitely something I plan to work on, but most of my attention is on the core of the plugins right now.
2. Are you assuming PTP 1.x or 2.x?
Presently development is for PTP 1.x. The only reason I haven't moved on to 2.x is that TAU users really require Fortran support. Once Photran is available for Eclipse 3.3 I will move to PTP 2.x as quickly as I can. I suspect that most of the work I am putting in right now will port over to
2.x (and the latest Eclipse and CDT) without too much difficulty. Supporting the new CDT launch and build systems will probably be the majority of the work.
3. Do you have any timeline for when you'd like to provide a release?
The plugins have been included with TAU for the last several releases. At this point the core features are fairly stable and usable. My concern with an official Eclipse-side release is that the architecture of the plugins is still in flux. For example, the tool xml file format is probably going to change a lot before it stabilizes. Pulling the TAU specific stuff out and leaving the basic generic components would not take long, however I am less sure about the timeline for completing generalization of the TAU specific elements, which is how I would rather handle it. Besides tool-genericness, are there any features or attributes you think should be in place for a (beta) release? Is there a time by which you think a release would be especially appropriate?
Thanks,
Wyatt
Regards,
Greg
On Oct 4, 2007, at 5:39 PM, wspear wrote:
Greetings,
Thanks to Beth's diligent efforts the current set of performance analysis plugins are now up on CVS. The improvements and various bugfixes are listed over on the eclipsezilla entry (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=168292). Quite a lot has changed since the last CVS commit but one of the most exciting new features is the ability for the user to specify his or her own performance tools, weather they are compiler wrappers, execution utilities of performance data analysis tools, for use in a basic performance analysis work-flow.
I intend to have an updated entry on the PTP wiki soon detailing the new functionality. The current entry (
http://wiki.eclipse.org/PTP/designs/perf_tools_framework/TAU ) remains accurate with respect to the TAU-specific functionality.
There is still a lot to be done and things are being added and adjusted fairly quickly. The next patch should include better support for specifying the output and analysis of performance data. Additional features in the works include support for database-enabled storage and display of profile data types in addition to TAU's, support for tool-specific environment variable configuration, EFS compatibility and user defined tool configuration tabs in the launch configuration manager.
If anyone wants help installing and using the plugins please let me know. Questions, comments or feedback on the performance plugins are encouraged. Development is quite flexible at this point so this is a good time to provide suggestions.
Regards,
Wyatt Spear
_______________________________________________
ptp-dev mailing list
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
