Athena Developer Guide

Athena Chapter 13 Framework services Version/Issue: 2.0.0
13.6 The Chrono & Stat service
The Chrono & Stat service provides a facility to do time profiling of code (Chrono part) and to do some
statistical monitoring of simple quantities (Stat part). The service is created by default by the
Application Manager, with the name “ChronoStatSvc” and service ID extern const CLID&
IID_IChronoStatSvc To access the service from inside an algorithm, the member function
chronoSvc() is provided. The job options to configure this service are described in Appendix B,
Table B.19.
13.6.1 Code profiling
Profiling is performed by using the chronoStart() and chronoStop() methods inside the codes
to be profiled, e.g:
/// ...
IChronoStatSvc* svc = chronoSvc();
/// start
svc->chronoStart( "Some Tag" );
/// here some user code are placed:
...
/// stop
svc->chronoStop( "SomeTag" );
The profiling information accumulates under the tag name given as argument to these methods. The
service measures the time elapsed between subsequent calls of chronoStart() and
chronoStop() with the same tag. The latter is important, since in the sequence of calls below, only
the elapsed time between lines 3 and 5 lines and between lines 7 and 9 lines would be accumulated.:
1: svc->chronoStop("Tag");
2: svc->chronoStop("Tag");
3: svc->chronoStart("Tag");
4: svc->chronoStart("Tag");
5: svc->chronoStop("Tag");
6: svc->chronoStop("Tag");
7: svc->chronoStart("Tag");
8: svc->chronoStart("Tag");
9: svc->chronoStop("Tag");
The profiling information could be printed either directly using the chronoPrint() method of the
service, or in the summary table of profiling information at the end of the job.
page 110
Note that this method of code profiling should be used only for fine grained monitoring inside
algorithms. To profile a complete algorithm you should use the Auditor service, as described in section
13.7.