Performance of org.eclipse.jdt.debug: I20100608-0911 relative to R-3.5-200906111540 (201006181800)

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() (vs. R-3.5-200906111540_201006111800)	+3.6% [±1.0]	- 6.1% [±0.7]	- 3.5% [±0.9]	- 0.5% [±0.7]
*PerfBreakpointTests#testLineBreakpointCreation() (vs. R-3.5-200906111540_201006111800)	- 1.8% [±2.0]	- 3.3% [±2.5]	- 5.5% [±2.1]	- 4.8% [±1.6]
*PerfBreakpointTests#testMethodEntryBreakpointCreation() (vs. R-3.5-200906111540_201006111800)	- 4.1% [±1.0]	- 1.2% [±0.8]	- 7.1% [±0.5]	- 3.7% [±0.6]
*PerfBreakpointTests#testWatchpointCreation() (vs. R-3.5-200906111540_201006111800)	- 4.9% [±1.2]	- 5.6% [±1.0]	- 6.8% [±0.9]	Performance criteria not met when compared to 'R-3.5-200906111540_201006111800': Elapsed Process= 0.59s is not within [0%, 110'%] of 0.52s - 12.5% [±0.7]
*PerfConditionalBreakpointsTests#testConditionalBreakpoints() (vs. R-3.5-200906111540_201006111800)	+0.0% [±6.6]	- 7.1% [±5.4]	+4.4% [±5.8]	+0.0% [±3.5]
*PerfConsoleTests#testProcessConsolePlainOutput10000Lines() (vs. R-3.5-200906111540_201006111800)	- 2.1% [±1.5]	- 2.5% [±2.4]	- 2.4% [±0.6]	+0.0% [±1.1]
*PerfConsoleTests#testProcessConsoleStackTraceOutput10000Lines() (vs. R-3.5-200906111540_201006111800)	+1.7% [±1.7]	+0.9% [±1.9]	- 3.5% [±1.0]	- 4.4% [±0.9]
*PerfConsoleTests#testProcessConsoleWrappedOutput10000Lines() (vs. R-3.5-200906111540_201006111800)	+0.5% [±1.5]	+3.3% [±1.7]	+1.4% [±0.7]	+1.8% [±1.7]
*PerfContextualLaunchMenu#testContextualLaunchMenu() (vs. R-3.5-200906111540_201006111800)	- 2.9% [±6.0]	- 1.4% [±7.5]	Performance criteria not met when compared to 'R-3.5-200906111540_201006041800': Elapsed Process= 23ms is not within [0%, 110'%] of 17ms - 9.5% [±17.2]	- 7.1% [±11.3]
*PerfSteppingTests#testBareStepOver() (vs. R-3.5-200906111540_201006111800)	+0.2% [±0.4]	- 9.6% [±0.4]	+0.0% [±0.2]	+2.8% [±0.1]
*PerfVariableDetailTests#testToStringDetails() (vs. R-3.5-200906111540_201006111800)	- 2.9% [±0.7]	- 6.6% [±0.6]	- 3.0% [±0.6]	+0.0% [±0.5]