Performance of org.eclipse.team: M20090917-0800 relative to R-3.4-200806172000 (200909141800)

Back to global results

The following fingerprints show results for the most representative tests of the org.eclipse.team component.

Select which kind of scale you want to use:

Help on fingerprints

Scenario Status

The following table gives a complete but compact view of performance results for the component.
Each line of the table shows the results for one scenario on all machines.

The name of the scenario is in bold when its results are also displayed in the fingerprints
and starts with an '*' when the scenario has no results in the last baseline run.

Here are information displayed for each test (ie. in each cell):

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]'.

Hints:

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 17 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)
SyncTests#testSync100NoUI()AddedFiles	- 8.5% [±1.3]	- 1.9% [±2.1]	+4.0% [±7.3]
SyncTests#testSync100NoUI()ModifiedFiles	+25.4% [±2.7]	+24.3% [±1.9]	+7.2% [±8.1]
SyncTests#testSync100NoUI()RemovedFiles	+3.4% [±6.2]	+20.0% [±2.9]	- 1.6% [±9.1]
WorkflowTests#testBigWorkflowNoUI()Checkout	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 5.4s is not within [0%, 110'%] of 4.8s - 11.7% [±11.8]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 5s is not within [0%, 110'%] of 3.6s - 37.0% [±15.1]	+2.6% [±4.8]
WorkflowTests#testBigWorkflowNoUI()Commit1	+1.0% [±18.0]	+20.0% [±12.1]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 2.5s is not within [0%, 110'%] of 2.2s - 14.7% [±11.2]
WorkflowTests#testBigWorkflowNoUI()Commit2	- 1.4% [±15.0]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 2.8s is not within [0%, 110'%] of 2.5s - 15.7% [±9.8]	- 7.0% [±7.7]
WorkflowTests#testBigWorkflowNoUI()Commit3	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 1.7s is not within [0%, 110'%] of 1.4s - 26.9% [±13.4]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 2.1s is not within [0%, 110'%] of 1.7s - 28.1% [±7.9]	+10.0% [±8.5]
WorkflowTests#testBigWorkflowNoUI()Commit4	- 8.4% [±12.4]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 2.7s is not within [0%, 110'%] of 2.4s - 14.7% [±9.8]	- 4.4% [±7.6]
WorkflowTests#testBigWorkflowNoUI()Replace1	+22.3% [±16.8]	+44.4% [±7.6]	+41.0% [±8.3]
WorkflowTests#testBigWorkflowNoUI()Replace2	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 3.6s is not within [0%, 110'%] of 2.7s - 35.7% [±24.0]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 3.1s is not within [0%, 110'%] of 1.2s - 150.7% [±40.3]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 3.8s is not within [0%, 110'%] of 2.2s - 72.6% [±23.3]
WorkflowTests#testBigWorkflowNoUI()Replace3	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 2.3s is not within [0%, 110'%] of 1.8s - 25.8% [±18.2]	+13.4% [±17.2]	Performance criteria not met when compared to 'R-3.4-200806172000_200909141800': Elapsed Process= 2.8s is not within [0%, 110'%] of 2.3s - 24.0% [±13.6]
WorkflowTests#testBigWorkflowNoUI()Share	+22.5% [±8.9]	+31.9% [±8.4]	+2.7% [±4.6]
WorkflowTests#testBigWorkflowNoUI()Tag1	+32.8% [±19.7]	+20.1% [±14.1]	+5.6% [±24.0]
WorkflowTests#testBigWorkflowNoUI()Update1	- 3.2% [±8.8]	- 0.7% [±6.8]	+1.3% [±6.2]
WorkflowTests#testBigWorkflowNoUI()Update2	+1.4% [±7.5]	+9.8% [±8.0]	+13.5% [±6.5]
WorkflowTests#testBigWorkflowNoUI()Update3	+4.0% [±8.3]	+2.1% [±6.9]	+6.2% [±7.1]
WorkflowTests#testBigWorkflowNoUI()Update4	- 3.4% [±7.9]	+9.0% [±4.5]	+12.6% [±3.8]

Performance of org.eclipse.team: M20090917-0800 relative to R-3.4-200806172000 (200909141800)

Scenario Status

All 17 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)