Project

General

Profile

Feature #939

Print cumulative timing information for each module at end of job when Timing service is used

Added by Brian Rebel almost 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Event Loop
Target version:
Start date:
02/07/2011
Due date:
09/30/2013
% Done:

100%

Estimated time:
16.00 h
Spent time:
Scope:
Internal
Experiment:
-
SSI Package:
Duration: 967

Description

It would be nice to have a summary of the amount of time spent in each module printed at the end of a job, with wall time, user time and system time, ie

Module1: xxx/yyy/zzz
Module2: xxx/yyy/zzz

etc.

History

#1 Updated by Rob Kutschke almost 10 years ago

I would like to add to this request. I would like to have the same info printed at different times and the option to configure any/all of the printout:

1) During each event at the end of each module so that we can find nasty events. ( Like the existing timer service ).
2) Per module once at the end of the job (Brian's request)
3) Summed over all modules, once at the end of the job.

Can the printout be decorated to make it easy to parse to build statistics over many jobs? Alternatively does it make sense to have any of the above written to the event-data output file? Not sure yet if I really want this since there will be jobs without event-data output file and other jobs with many such files.

#2 Updated by Walter E Brown almost 9 years ago

  • Status changed from New to Accepted

#3 Updated by Brian Rebel about 8 years ago

Could we have the ability to turn on more statistics on a module by module basis to give a max time used, min time used, mean and rms?

#4 Updated by Christopher Green over 7 years ago

  • Due date set to 09/30/2013
  • Category set to Event Loop
  • Target version set to 1.09.00
  • Estimated time set to 16.00 h
  • Scope set to Internal
  • Experiment - added

#5 Updated by Christopher Green almost 7 years ago

  • Target version changed from 1.09.00 to 521

#6 Updated by Christopher Green over 6 years ago

  • Target version changed from 521 to 1.10.00

#7 Updated by Christopher Green over 6 years ago

  • Target version changed from 1.10.00 to 1.14.00

#8 Updated by Christopher Green over 6 years ago

  • Target version changed from 1.14.00 to 1.13.00

#9 Updated by Kyle Knoepfel almost 6 years ago

  • Assignee set to Kyle Knoepfel

#10 Updated by Kyle Knoepfel almost 6 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

This feature request has been resolved as described in issue #3598. We have elected to not provide separate user- and system-time quantities, which can be determined only by calling a function that we think is rather expensive. Instead, we have added a new service called TimeTracker, which provides a more descriptive printout that includes the minimum, maximum, mean, median, and root-mean-square of time taken to execute a full event or a specific module.

Implemented with e7078a47887c46d97e977b05f4f985b0cc5b3aec.

#11 Updated by Christopher Green almost 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF