Project

General

Profile

Bug #2979

strange Timing_service printout

Added by Andrei Gaponenko over 7 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Kyle Knoepfel
Category:
Infrastructure
Target version:
1.13.00
Start date:
Due date:
09/30/2013
% Done:

100%

Estimated time:
16.00 h
Spent time:
1.00 h
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

Hello,

I got a Timing printout at the end of the job with "Avg" greater than "Max", which does not look right.

Andrei

TimeReport ---------- Time Summary ---[sec]----
TimeReport CPU = 618.437983 Real = 618.577552

TimeReport> Time report complete in 787.885 seconds
Time Summary:
Min: 121.656
Max: 126.523
Avg: 157.577

Related issues

Related to art - Feature #3598: Obtaining more information from Timing serviceClosed03/13/201309/30/2013

Associated revisions

Revision 82b0f90a (diff)
Added by Kyle Knoepfel about 5 years ago

Fix for issue #2979; some tidying.

History

#1 Updated by Christopher Green over 6 years ago

  • Due date set to 09/30/2013
  • Category set to Infrastructure
  • Target version set to 1.09.00
  • Estimated time set to 16.00 h
  • Scope set to Internal
  • Experiment - added
  • SSI Package art added

Timing service should be reviewed and tested for correct behavior under SLF5 and SLF6. There are rumors that a behavior problem was found and fixed by CMS: this should be verified.

#2 Updated by Christopher Green over 6 years ago

  • Status changed from New to Accepted
  • Start date deleted (10/02/2012)

#3 Updated by Christopher Green about 6 years ago

  • Target version changed from 1.09.00 to 521

#4 Updated by Christopher Green almost 6 years ago

  • Target version changed from 521 to 1.10.00

#5 Updated by Christopher Green almost 6 years ago

  • Target version changed from 1.10.00 to 1.14.00

#6 Updated by Christopher Green almost 6 years ago

  • Target version changed from 1.14.00 to 1.13.00

#7 Updated by Kyle Knoepfel about 5 years ago

  • Assignee set to Kyle Knoepfel

#8 Updated by Kyle Knoepfel about 5 years ago

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

The behavior you observed resulted from an incorrect calculation of the mean, which is particularly noticeable when a small number of events is processed. The correct calculation is now used for the average.

Fixed with 82b0f90a8eda2936cf18e9e450a6419ad58a39da.

#9 Updated by Christopher Green about 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF