TIME_MEASUREMENT macro
In a lot places a TIME_MEASUREMENT
macro is set to measure the time spent in a function. Is this still needed or can it be removed? For performance comparisons other methods might be more suitable.
In a lot places a TIME_MEASUREMENT
macro is set to measure the time spent in a function. Is this still needed or can it be removed? For performance comparisons other methods might be more suitable.
added discussion low refactoring labels
Depends what you want to do with the obtained time measures. If you want to decide if a new implementation is faster/slower as the current on the high_resolution_clock
might be sufficient.
But for deeper analysis (e.g., publications) tools as perf
, gprof
, Scalasca
(FZ developed), PAPI
yield more reliable results. But are also more difficult to use.
added To Do label
removed To Do label
changed milestone to %1.0.0 - old
added low-effort label and removed low label
added low label
mentioned in merge request !264 (merged)
closed with merge request !264 (merged)
mentioned in commit d384121f