Model building statistics in Omedit

[anonymous]

OpenModelicaUsersGuide.pdf in section 1.2.5 shows simulation of a DC motor and displays interesting timing statistics:

timeFrontend = 0.244445734,
timeBackend = 0.011048542,
timeSimCode = 0.042049415,
timeTemplates = 0.027458789,
timeCompile = 0.394855691,
timeSimulation = 0.014914653,
timeTotal = 0.7349152410000001

When models are compiled and run from OMEdit only statistics related to the final running of the model are available.
Is it possible to find a way to convey also these timings in the OMEdit output?
Very often (as in the DC motor example) more time is spent in preparing the final executable than in the execution itself.

[Martin Sjölund]

You can set debug-flag -d=execstat in OMEdit to display this information (and more):

[71] 15:26:42 Translation Notification
Performance of simCode: all other stuff during SimCode phase: time 0.008629/0.01681, allocations: 0.6835 MB / 98.62 MB, free: 4.52 MB / 10.5 MB

Although I guess having a few dozens of lines in the log can get a bit annoying...

[anonymous]

Thank you for the information.
The way you suggest works, even though, I think, the final user would expect to see timing statistics, including model preparation, directly in the final prospect under the "timer" item. I mean limited number (say one to three) of rows more in the beginning of that prospect.

The statistics got with the flag seems more for developers than users.

The statistic outputs, in addition of being large, are not very clear to me. Consider this example:

[7] 15:21:46 Translation Notification
Performance of FrontEnd: time 1.296/2.109, allocations: 53.47 MB / 4.017 GB, free: 114.2 MB / 490.7 MB

How to interpret the times? The time used by frontend activities is 1.296s or 2.109s?
Naturally if you answer this question here I will be glad, out other users might not know the answer.
Nor Want I suggest to explain the meaning of all the execstats in the user manual under the execstat debug flag, since it would take pages. This confirms that the solution of using this flag is not intended for the final OM/OMEdit user.

And that, maybe, one to three more rows in the final OMEdit prospect under "timer" would be really useful.

[anonymous]

Well, I said 1-to-three rows.
Maybe the best solution is to give through the final OMEdit prospect the same information as in the description of this ticket, since it is already supplied by OMC, or something near to that.

[Francesco Casella]

I agree with the anonymous reporter: normal end users are not interested in the full -d=execstat report, but would definitely appreciate getting the summary reported at the beginning of this ticket.