Revise the Timer system to provide better time logging facilities
The present Timer
system has some drawbacks, especially in parallel.
Some features which would be nice:
- Knowledge of nested timers, so the same piece of code is not counted twice
- Machine readable output format, for plotting graphs
- Aggregation of timers in parallel, to produce a single output
- Max/min/average calculation for each timer
Both boost
and Eigen
(required dependencies) have nice timers available.
Comments (13)
-
-
C++11 has some new timing facilities too.
I use Boost timer, but the downside is that it's not header-only which adds a little extra complication to the build and configure process.
-
- changed status to open
-
- changed component to common
-
reporter -
assigned issue to
-
assigned issue to
-
reporter This issue could be closed. Only one small thing - @blechta - the deprecation message for
list_timings()
in Python is not very helpful.The replacement for
list_timings()
islist_timings(TimingClear_clear, [TimingType_wall])
? -
It is
list_timings(TimingClear_keep, [TimingType_wall])
I think. Do you suggest to keeplist_timings()
executinglist_timings(TimingClear_clear, [TimingType_wall])
or just improving deprecation message? -
reporter Your choice - it is just a bit confusing for Python users at the moment...
-
Remainder for me: doc is not generated for
enum class TimingClear
andenum class TimingType
, both in C++ and Py.Fix possibly here.
-
- changed milestone to 1.6
-
Fix in next 2575751
-
- changed status to resolved
Should be resolved by 831ab0d
-
- removed milestone
Removing milestone: 1.6 (automated comment)
- Log in to comment
Yes, good points.