Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353980

Summary:	[Performance] Setting up a performances measures and non regression project
Product:	[Modeling] EMFCompare	Reporter:	Cedric Brun <cedric.brun>
Component:	Core	Assignee:	EMF Compare <emf.compare-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mikael.barbero
Version:	unspecified
Target Milestone:	Mars
Hardware:	PC
OS:	Linux
Whiteboard:

Description Cedric Brun

2011-08-05 05:15:29 EDT

You don't control what you can't *measure*. Performance is *key aspect* of model comparison. 

We used to work on performance but without constant checking we quickly loose the gain when changing code or integrating contributions.

Let's work on having good measures of performances and scalability, and then we'll be able to check whether we have improvements or regressions.

This framework (https://github.com/Obeo/fr.obeo.performance) has been initiated by Obeo guys to ease the measure and at some point, the reporting of these measures. It's EPL but it's not in Eclipse or has no CQ so far, meaning our performance test suite should be kept separate from the Eclipse repository for now.

Comment 1 Cedric Brun

2011-08-05 05:47:57 EDT

I created a repo here :https://github.com/cbrun/emf.compare.performance

Comment 2 Mikaël Barbero

2014-08-21 08:26:45 EDT

While this is certainly not perfect, https://hudson.eclipse.org/emfcompare/job/master-performance/ has been set up and keep track of performance with nice diagramming https://hudson.eclipse.org/emfcompare/job/master-performance/ws/performance/org.eclipse.emf.compare.tests.performance/index.html.

Improvement requests to these tests should be done in a new bug.