Bug 71123

Description Jim des Rivieres 2004-07-29 17:43:10 EDT

Process improvements wrt performance. For 3.1 we should get a firm grip on 
speed and space performance. To do this we should (1) identify which aspects 
are critically important performance-wise; (2) establish benchmarks to 
quantify performance; and (3) look at ways to improve performance. By its 
nature, it's hard to say in advance what kind of improvements we'll be able to 
achieve, making it difficult to make performance improvements a release 
deliverable. Instead, what we need to do for 3.1 is commit to track 
performance from this point on. We should carry out performance reviews (1) 
and create benchmarks (2) for every component, and for any critical aspects 
that span components. Even if we cannot find ways to make significant 
performance gains (3), the benchmarks are still critical to Eclipse's success 
to prevent backsliding in the future. The work item is to improve our process 
with respect to performance. The deliverables are the automated performance 
tests, the build process that collects and publishes performance data covering 
all critical aspects of Eclipse, and the committment to leverage this data to 
monitor speed and space performance as part and parcel of developing Eclipse. 
[All Eclipse components]