Performance of org.eclipse.jdt.debug: M20100908-0800 relative to R-3.5-200906111540 (201008301800)

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 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 6.0_04 (2 x 3.00GHz - 3GB RAM)
PerfBreakpointTests#testBreakpointRemoval()	+2.4% [±1.1]	- 6.1% [±0.7]	+1.0% [±0.9]	+0.0% [±0.7]
PerfBreakpointTests#testLineBreakpointCreation()	+0.3% [±2.1]	- 7.6% [±1.9]	- 6.0% [±1.6]	- 3.5% [±2.4]
PerfBreakpointTests#testMethodEntryBreakpointCreation()	+1.2% [±0.8]	- 7.6% [±0.6]	- 2.3% [±0.5]	- 4.5% [±0.3]
PerfBreakpointTests#testWatchpointCreation()	- 0.6% [±1.1]	- 9.5% [±0.9]	- 2.9% [±0.8]	Performance criteria not met when compared to 'R-3.5-200906111540_201008301800': Elapsed Process= 0.57s is not within [0%, 110'%] of 0.52s - 10.2% [±0.7]
PerfConditionalBreakpointsTests#testConditionalBreakpoints()	- 2.2% [±7.3]	Performance criteria not met when compared to 'R-3.5-200906111540_201008231800': Elapsed Process= 0.11s is not within [0%, 110'%] of 93ms - 15.1% [±5.8]	- 2.8% [±6.0]	- 1.8% [±3.3]
PerfConsoleTests#testProcessConsolePlainOutput10000Lines()	- 2.8% [±1.6]	+3.9% [±1.8]	- 1.2% [±0.6]	- 3.9% [±1.2]
PerfConsoleTests#testProcessConsoleStackTraceOutput10000Lines()	+0.8% [±1.5]	+1.0% [±2.2]	- 3.0% [±1.0]	- 2.9% [±0.8]
PerfConsoleTests#testProcessConsoleWrappedOutput10000Lines()	+1.3% [±1.4]	+4.6% [±2.0]	+2.3% [±0.6]	- 1.8% [±1.6]
PerfContextualLaunchMenu#testContextualLaunchMenu()	+1.4% [±7.3]	+2.8% [±7.7]	+10.0% [±15.6]	+11.8% [±9.1]
PerfSteppingTests#testBareStepOver()	+1.0% [±0.3]	Performance criteria not met when compared to 'R-3.5-200906111540_201008231800': Elapsed Process= 0.6s is not within [0%, 110'%] of 0.54s - 11.4% [±0.4]	- 1.0% [±0.2]	- 4.3% [±0.2]
PerfVariableDetailTests#testToStringDetails()	+0.0% [±0.7]	- 6.5% [±0.7]	- 1.5% [±0.6]	- 1.6% [±0.5]