Scenario: org.eclipse.core.tests.runtime.perf.ContentTypePerformanceTest#testLoadCatalog() (RHEL 4.0 Sun 1.4.2_10 (3 GHz 2.5 GB))
Note:
Loading the content types traverses all extensions to the content type extension point, and that operation became more expensive in 3.1. Thankfully, it happens only once per session.
Raw data and Stats
Click measurement name to view line graph of measured values over builds.
| Build Id | Elapsed Process | CPU Time |
| M20080911-1700 | 44ms | 50ms |
| 3.3_200706251500_200806171530 (reference) | 84ms [0ms] | 89ms [7ms] |
| *Delta | 40ms
47.6 % | 39ms
43.8 % |
*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
Elapsed Process
CPU Time
CPU Time
