[news.eclipse.tools.hyades] Extreme performance degradation while profil

["Dave Kelsey" <dkelsey@xxxxxxxxxxxxxxxxx>]

We have a very CPU intensive Eclipse plugin. It is driven from a menu popup
and it takes about 35-40 seconds to complete it's activity.

We wanted to profile this execution to determine if we can improve the
performance so using Hyades 3.0 and Eclipse 3.0 we launched it to capture
execution time information. We had setup filters to only capture information
within our plugin classes and we only start profiling just before we invoke
the popup menu option. I have confirmed that we only capture information
about our classes. However we gave up trying to get a full run. What took
35-40 seconds without profiling went to 40 minutes and still had not
finished.

Given that we have setup the filters to only capture our classes and that we
are only collecting execution time analysis with show execution statistics
on a local machine (launched through eclipse), is there anything else we can
do to improve the time taken to collect the information ? This is only a
simple test, we want to profile on a much larger data set of information
that takes about 5 minutes to process but given the markup by hyades
profiling, this could take some hours to collect. Maybe writing the
information to a file and importing it ? There is no real documentation on
how to do this.

Any help on this would be great

Thanks
Dave Kelsey.