Community
Participate
Working Groups
the org.eclipse.test.performance plug-in allows unit tests to persist resource usage to a database, and to make assertions about resource usage. It also includes a report generation facility for generating graphs of performance over time. I'd like to enable this in the cdt overnight build, and aim to start work on this soon
I've got this working on my local linux box, the one remaining issue seems to be that when the report generation utility is launched, it thinks its running on (linux,x86,motif) rather than (linux,x86,gtk) and fails to resolve its bundle dependencies
Created attachment 55148 [details] adds the necessary parts to the releng and test plugins to enable the performance test framework this patch adds the necessary parts to the releng and test plugins to enable the performance test framework see http://www.eclipsecon.org/2005/presentations/EclipseCon2005_13.2ContinuousPerformance.pdf for details of the framework Its not quite in the form I tested it in as I had to adapt the map files to use the COPY fetch factory rather than go via CVS the build.sh script will now fail unless eclipseDist and eclipse.perf.dbloc are both set. This will not stop people running the build locally but they would need to specify a dummy location to write performance data to (e.g. /var/tmp/cdtperfDB) the patch includes a DemoPerformanceTest that shows how this could be used the two questions left are (1) the performance test results are generated as php files - are these supported in the current location? for example, the server supports them here http://download.eclipse.org/eclipse/downloads/drops/R-3.2.1-200609210945/performance/performance.php (2) what do we use a baseline for performance comparison? the presentation above suggests branching a known good build, and back-porting performance tests to this. I'm not sure how this would relate to CDT 4.0..
