Performance Results

Performance fingerprint

Performance of M20160212-1500 relative to R (201509040015)

The following fingerprints show results for the most representative tests of the current build.
Select which kind of scale you want to use:
Help on fingerprints

SUSE Linux Enterprise Server 11 (x86_64)

Legend:
*: Missing reference data. Build used for comparison specified in ending parenthesis.
green: faster, less memory
red: slower, more memory
grey: regression with explanation. Click the bar for notes on this scenario.
x axis: difference between current value and baseline value as percentage

Detailed performance data grouped by scenario prefix

org.eclipse.ant*
org.eclipse.compare*
org.eclipse.core*
org.eclipse.jdt.core*
org.eclipse.jdt.debug*
org.eclipse.jdt.text*
org.eclipse.jdt.ui*
org.eclipse.jface*
org.eclipse.pde.api.tools*
org.eclipse.pde.ui*
org.eclipse.swt*
org.eclipse.team*
org.eclipse.ua*
org.eclipse.ui*

Performance Unit Test Results for 4.5.2

The table shows the unit test results for this build on the platforms tested. You may access the test results page specific to each component on a specific platform by clicking the cell link. Normally, the number of errors is indicated in the cell. A "-1" or "DNF" means the test "Did Not Finish" for unknown reasons and hence no results page is available. In that case, more information can sometimes be found in the console logs.

See also the baseline unit tests results.

org.eclipse
Component
Test Configurations
linux.gtk.x86_64_8.0 macosx.cocoa.x86_64_7.0 win32.win32.x86_7.0
ant.tests.*

ant.tests.ui

(0) (XML)--
compare.tests(0) (XML)--
core.tests.*

core.tests.resources

(0) (XML)--

core.tests.runtime

(4) (XML)--
jdt.core.tests.*

jdt.core.tests.performance

(1) (XML)--
jdt.debug.tests(0) (XML)--
jdt.text.tests(26) (XML)--
jdt.ui.tests.*

jdt.ui.tests.refactoring

(0) (XML)--

jdt.ui.tests

(0) (XML)--
pde.api.tools.tests(0) (XML)--
pde.ui.tests(0) (XML)--
swt.tests(0) (XML)--
team.tests.*

team.tests.cvs.core

(2) (XML)--
ua.tests(2) (XML)--
ui.tests.*

ui.tests.forms

(0) (XML)--

ui.tests.performance

(2) (XML)

NOTE: Remember that for performance unit test tables, there are never any "missing files" listed, if there are any. This is expected to be a temporary solution, until an exact fix can be implemented. For more details, see bug 451890.