Performance of org.eclipse.jdt.debug: I20070625-1500 relative to 3.2

RHEL 4.0 Sun 1.4.2_10 (3 GHz 2.5 GB)

Win XP Sun 1.4.2_10 (3 GHz 2 GB)

RHEL 3.0 Sun 1.4.2_10 (3 GHz 2 GB)

Win XP Sun 1.4.2_10 (2 GHz 512 MB)

RHEL 3.0 Sun 1.4.2_10 (2 GHz 512 MB)

Scenario Status

• an icon showing whether the test fails or passes and whether it's reliable or not.
  The legend for this icon is:
  • Green (): mark a successful result, which means this test has neither significant performance regression nor significant standard error
  • Red (): mark a failing result, which means this test shows a significant performance regression (more than 10%)
  • Gray (): mark a failing result (see above) with a comment explaining this degradation.
  • Yellow ( or ): mark a failing or successful result with a significant standard error (more than 3%)
  • Black (): mark an undefined result, which means that deviation on this test is not a number (NaN) or is infinite (happens when the reference value is equals to 0!)
  • "n/a": mark a test for with no performance results
• the value of the deviation from the baseline as a percentage (ie. formula is: (build_test_time - baseline_test_time) / baseline_test_time)
• the value of the standard error of this deviation as a percentage (ie. formula is: sqrt(build_test_stddev^2 / N + baseline_test_stddev^2 / N) / baseline_test_time)
  When test only has one measure, the standard error cannot be computed and is replaced with a '[n/a]'.

• fly over image of failing tests to see the complete error message
• to look at the complete and detailed test results, click on its image

All 11 scenarios	RHEL 3.0 Sun 1.4.2_10 (2 GHz 512 MB)	RHEL 3.0 Sun 1.4.2_10 (3 GHz 2 GB)	RHEL 4.0 Sun 1.4.2_10 (3 GHz 2.5 GB)	Win XP Sun 1.4.2_10 (2 GHz 512 MB)	Win XP Sun 1.4.2_10 (3 GHz 2 GB)
PerfBreakpointTests#testBreakpointRemoval()	+5.5% [±0.9]	+1.7% [±0.9]	+9.9% [±0.6]	+5.1% [±0.7]	+4.5% [±0.6]
PerfBreakpointTests#testLineBreakpointCreation()	+1.6% [±0.4]	- 1.0% [±0.5]	+4.0% [±0.5]	+8.2% [±0.6]	+2.7% [±0.3]
PerfBreakpointTests#testMethodEntryBreakpointCreation()	+0.7% [±0.3]	- 0.5% [±0.3]	+2.1% [±0.2]	+6.9% [±0.2]	+1.9% [±0.3]
PerfBreakpointTests#testWatchpointCreation()	+0.0% [±0.7]	+1.0% [±0.7]	+2.1% [±0.4]	+4.6% [±0.7]	- 0.2% [±0.8]
PerfConditionalBreakpointsTests#testConditionalBreakpoints()	+1.0% [±3.6]	+0.6% [±4.6]	- 7.2% [±5.8]	+6.0% [±2.6]	+8.8% [±3.0]
PerfConsoleTests#testProcessConsolePlainOutput10000Lines()	- 4.8% [±0.7]	+0.0% [±1.6]	+2.9% [±1.1]	- 5.0% [±1.6]	- 2.8% [±0.9]
PerfConsoleTests#testProcessConsoleStackTraceOutput10000Lines()	- 6.3% [±0.9]	- 3.3% [±1.3]	+6.2% [±1.4]	+0.0% [±1.3]	+1.1% [±1.1]
PerfConsoleTests#testProcessConsoleWrappedOutput10000Lines()	- 8.2% [±0.7]	+1.2% [±1.5]	+5.7% [±1.2]	Performance criteria not met when compared to '{config=eclipseperfwin1_R3.3, build=3.2_200606291905_200706111606, jvm=sun}': Elapsed Process: 1.41s is not within [0%, 110%] of 1.22s - 15.5% [±1.7]	- 4.1% [±1.2]
PerfContextualLaunchMenu#testContextualLaunchMenu()	+89.4% [±3.7]	+88.9% [±13.3]	+87.3% [±11.7]	+96.8% [±7.9]	+94.1% [±14.8]
PerfSteppingTests#testBareStepOver()	- 2.6% [±0.5]	- 0.8% [±0.3]	+0.6% [±0.1]	+3.5% [±0.3]	- 0.7% [±0.3]
PerfVariableDetailTests#testToStringDetails()	+28.8% [±0.6]	+24.3% [±0.5]	+27.0% [±0.4]	+24.9% [±0.3]	+23.1% [±0.4]