[News.eclipse.test-and-performance] Re: How about testing performance of

["Harm Sluiman" <sluiman@xxxxxxxxxx>]

I think Chris is specifically talking about performance profiling.
As Java has evolved (eclipse is a good example) the amount of tracing data that
can be involved to build performance metrics has grown. The profiling abilities
in Hyades focused on distributed applications rather than large clients or the
app servers themselves. However over time the desire to address both with Hyades
has come up time and time again. The scalability of the Hyades profiler has
improved 2 orders of magnitude over the last year and is still improving. We
also intend to add sampling based profiling, and have had requests to also
target languages like C/C++.
I am familiar with some of Chris' work and there is definitely room to bring
some of the collection and visualization ideas into the performance profiling
sub-project. We need to do the detailed work to see how a merge can be done to
get the best of both worlds. In the end there are some very explicit platform
specific things that may be needed but those can be in separate plugins on top
of the rest of the merged capabilities. Hyades does need to address all sizes of
applications and collected data.



"Mike Norman" <mgn@xxxxxxxxxxxxx> wrote in message
news:41002DDA.7030507@xxxxxxxxxxxxxxxx
> Chris
>
> I know exactly what you mean. Hyades, for example, now provides some
> some tests defined in itself, but they don't have a clear relationship
> with the build process. This drifted in and out of scope of the
> discussions when we were building the project proposal. The feedback
> from the board in an early review cycle of the documents was that the
> includion of this in the project was not appropriate at  this time.
>
> The broad issue of concern here is the definition of builds, and then
> the testing thereof, and then the testing and certification of plugins
> against those builds. There are separate vendor builds and
> certifications in place or being developed and I think resolution at
> this level will have to precede the creation of a project. This is
> particularly problematic with the non-core elements, such as Hyades
> which may be included in one vendor's build and not another, and is a
> nightmare for plug-in vendors wishing to install into a number of
> vendors builds.
>
> Mike
>
> Chris Laffra wrote:
> > I think this top-level project would be a great host to a project focusing
> > explicitly on testing and performance profiling of Eclipse itself. The
> > core.tools tools should be moved into that project, in addition to the
> > automated regression test tools currently managed by the Eclipse build
> > team.
> >
> > I happen to have worked on Eclipse profiling tools that would be perfectly
> > hosted under this "Eclipse Plugin Performance" sub-project.
> >
> > Chris Laffra
> >
>