Project

General

Profile

Necessary Maintenance #7731

Determine if art summary TimeReport can be replaced by TimeTracker summary

Added by Kyle Knoepfel almost 6 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
01/30/2015
Due date:
% Done:

100%

Estimated time:
2.00 h
Spent time:
Scope:
Experiment:
SSI Package:
art
Duration:

Description

The current art summary includes a time tracker with various CPU/real-time measurements. The new TimeTracker service will do something similar, but only with real-time measurements. We should see if these two summaries can somehow be merged.


Related issues

Related to art - Necessary Maintenance #6339: Duplication of utility functionality in art vs cetlibClosed05/23/2014

Associated revisions

Revision e75def7b (diff)
Added by Kyle Knoepfel over 3 years ago

Resolve issue #7731: retain only job-level stopwatch.

History

#1 Updated by Christopher Green over 5 years ago

#2 Updated by Christopher Green over 5 years ago

  • Status changed from New to Accepted
  • Target version set to 1.14.00

A meeting will be scheduled to identify whether TimeTracker can / should be changed to support the worthwhile aspects of the current "TimeReport" summary (and what those worthwhile aspects are).

#3 Updated by Christopher Green over 5 years ago

  • Estimated time set to 2.00 h

#4 Updated by Kyle Knoepfel over 5 years ago

  • Target version deleted (1.14.00)

#5 Updated by Kyle Knoepfel over 5 years ago

  • Target version set to 521

#6 Updated by Ron Rechenmacher over 3 years ago

I'm seeing several (12) getrusage system calls at some point during event processing when I only have and output module specified.
If they can be eliminated or reduced, I may be able to get a significant performance gain.

#7 Updated by Kyle Knoepfel over 3 years ago

  • Priority changed from Low to Normal

#8 Updated by Kyle Knoepfel over 3 years ago

  • Project changed from cet-is to art
  • Category set to Infrastructure
  • Status changed from Accepted to Resolved
  • Assignee set to Kyle Knoepfel
  • Target version changed from 521 to 1209
  • % Done changed from 0 to 100
  • SSI Package art added

Per discussion at the stakeholders meeting on 5/19/2017, the job-level CPU time will still be captured, as that is helpful. However, the frequent CPU usage capturing at the event-level will be removed. If users want more detailed timing information, they should enable the TimeTracker service (which gives detailed per-module wall-clock times), or use a profiler (e.g. allinea).

Implemented with commit art:e75def7b.

#9 Updated by Kyle Knoepfel over 3 years ago

  • Target version changed from 1209 to 2.07.01

#10 Updated by Kyle Knoepfel over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF