id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2884	Performance tracing for compiler and simulation stages	Lennart Ochel	somebody	"I think it is necessary to trace the performance of both, the OpenModelica compiler, as well as the generated simulations. Therefore a new Hudson job could be added that runs a (small) set of models for each revision and measures the elapsed time for the different compiler and simulation stages:
* Compiler: Front end, back end (in total and for each optimization module), SimCode, …
* Simulation: Non-linear solvers, linear solvers, event iteration, …

Therefore, it is probably necessary to run this on an independent machine. 

Of course it would be also interesting to test different OS and hardware configurations… But that would be too much. I think for the beginning it is good enough to have at least one setup for the measurements.

The set of models should contain a couple of the biggest models from some libraries, as well as a couple of scalable models (that are probably some kind of artificial) to see if everything scales as expected and to detect bottlenecks and bad commits.

The results of such a performance tracing should be provided as a text summary and as intuitive graphs. With these results it would be possible to detect and fix much more efficiently a lot of performance issues. Also it would help to provide always an efficient OpenModelica build."	discussion	new	high	Future	*unknown*	trunk			Adrian Pop Martin Sjölund Adeel Asghar Volker Waurich Marcus Walther