Performance of org.eclipse.jdt.debug: M20110210-1200 relative to R-3.5-200906111540 (201102071800)

SLED 10 Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM)

RHEL 5.0 Sun 6.0_04 (2 x 3.00GHz - 3GB RAM)

Win XP Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM)

Win XP Sun 1.6.0_04 (2 x 3.00GHz - 3GB RAM)

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	SLED 10 Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM)	RHEL 5.0 Sun 6.0_04 (2 x 3.00GHz - 3GB RAM)	Win XP Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM)	Win XP Sun 1.6.0_04 (2 x 3.00GHz - 3GB RAM)
PerfBreakpointTests#testBreakpointRemoval()	+1.2% [±1.0]	- 4.8% [±0.7]	- 7.2% [±0.9]	- 5.6% [±0.7]
PerfBreakpointTests#testLineBreakpointCreation()	+0.9% [±1.6]	+0.9% [±1.2]	- 2.0% [±1.6]	- 6.7% [±1.1]
PerfBreakpointTests#testMethodEntryBreakpointCreation()	- 3.1% [±0.8]	- 5.3% [±0.7]	- 6.7% [±0.5]	Performance criteria not met when compared to 'R-3.5-200906111540_201102071800': Elapsed Process= 0.58s is not within [0%, 110'%] of 0.53s - 10.0% [±0.4]
PerfBreakpointTests#testWatchpointCreation()	- 4.8% [±1.1]	- 7.4% [±1.0]	- 7.5% [±0.8]	Performance criteria not met when compared to 'R-3.5-200906111540_201102071800': Elapsed Process= 0.59s is not within [0%, 110'%] of 0.53s - 10.7% [±0.7]
PerfConditionalBreakpointsTests#testConditionalBreakpoints()	- 1.1% [±8.1]	Performance criteria not met when compared to 'R-3.5-200906111540_201102071800': Elapsed Process= 0.1s is not within [0%, 110'%] of 95ms - 10.5% [±5.2]	- 5.8% [±6.8]	+0.9% [±4.0]
PerfConsoleTests#testProcessConsolePlainOutput10000Lines()	- 3.2% [±1.4]	+0.6% [±1.4]	- 3.4% [±0.5]	- 1.5% [±1.1]
PerfConsoleTests#testProcessConsoleStackTraceOutput10000Lines()	+0.7% [±1.5]	+3.6% [±1.4]	- 5.7% [±1.0]	+0.1% [±0.9]
PerfConsoleTests#testProcessConsoleWrappedOutput10000Lines()	- 1.9% [±1.5]	+2.9% [±1.2]	+0.1% [±0.6]	- 0.3% [±1.5]
PerfContextualLaunchMenu#testContextualLaunchMenu()	- 4.4% [±7.1]	- 4.3% [±7.7]	+0.0% [±16.5]	+0.0% [±15.5]
PerfSteppingTests#testBareStepOver()	+2.3% [±0.4]	Performance criteria not met when compared to 'R-3.5-200906111540_201102071800': Elapsed Process= 0.6s is not within [0%, 110'%] of 0.55s - 10.3% [±0.4]	- 5.1% [±0.2]	- 1.7% [±0.2]
PerfVariableDetailTests#testToStringDetails()	+2.9% [±0.6]	- 4.6% [±0.6]	- 3.0% [±0.6]	+0.0% [±0.5]