online: Move step timers into global reco class.

added Online mCBM labels

assigned to @fweig

added 1 commit

e088d2d4 - format

Compare with previous version

Dear @v.friese, @a.bercuci, @p.kaehler, @d.smith, @fweig,

you have been identified as code owner of at least one file which was changed with this merge request.

Please check the changes and approve them or request changes.

added CodeOwners label

What is the motivation for this change?

In my opinion, it would be beneficial to get an output of the processing time per step in the console log. Ideally, each step should deliver one line, with the proc. time, throughput and some basic numbers (like number of input and output data or whichever is considered meaningful). This is beneficial when running the application offline (for development, debugging and other purposes). That can hardly be achieved if the timer is moved outside of the step itself.

Another argument: Since for instance the trigger will be flexible (choose from a set of available trigger), the input data size might be different depending on the chosen trigger and its settings. So, the throughput cannot be calculated on the global reco level.