Scenario: org.eclipse.jdt.text.tests.performance.ActivateJavaEditorTest#testActivateEditor() (Win XP Sun 1.4.2_08 (3 Hz 2 GB))


*** WARNING *** There is not enough evidence to reject the null hypothesis at the 90% level (Student's t-test).
Notes
Java editor activation was not working correctly in 3.1 (see bug 119326 and bug 120572). The fixes result this expected performance degradation.



Raw data and Stats

Click measurement name to view line graph of measured values over builds.

Build Id Elapsed Process CPU Time GDI Objects
3.2_2006062919052.66s [283ms] 4.85s [380ms] 0
3.1_200506271435_200606231551(reference)2.49s [254ms] 4.54s [253ms] 0
*Delta169ms
6.7 %		313ms
6.8 %		0
*Delta values in red and green indicate degradation > 10% and improvement > 10%,respectively.


Black and yellow points plot values measured in integration and last seven nightly builds.
Magenta points plot the repeated baseline measurement over time.
Boxed points represent previous releases, milestone builds, current reference and current build.

Hover over any point for build id and value.

Elapsed Process
Amount of wall-clock time.



CPU Time
Amount of time the process ran on the CPU.



GDI Objects
Change in the number of GDI (Graphics Device Interface) objects, can be useful for UI tests (particularly start-up tests).