Scenario: org.eclipse.jdt.text.tests.performance.OpenJavaEditorStartupTest#testJavaEditorStartup() (Win XP Sun 1.4.2_08 (3 GHz 2 GB))


Notes
The startup with open Java editor performance has been decreased due to lazy plug-in and class loading

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

Build Id Elapsed Process CPU Time Kernel time GDI Objects
3.1_20050627143512.14 s 13.08 s 1.08 s 377
3.0_200406251208_200506241211(reference)9.81 s 10.92 s 687 ms 332
*Delta2.33 s
23.7 %		2.16 s
19.7 %		391 ms
56.9 %		45
13.5 %
*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.

Click here to view raw data and stats.
The raw data and stats include data for all current stream builds and all baseline test runs.


Elapsed Process
Amount of wall-clock time.



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



Kernel time
Amount of time the process ran on the CPU, while the CPU was in kernel mode.



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