Project

General

Profile

Feature #8131

Support #8103: Update to art 1.13.01: update deprecated features

Investigate the new Timing replacements

Added by Gianluca Petrillo over 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Low
Category:
Other
Target version:
-
Start date:
03/19/2015
Due date:
% Done:

100%

Estimated time:
4.00 h
Spent time:
Experiment:
-
Co-Assignees:
Duration:

Description

art 1.13 offers replacements for Timing module, that is considered deprecated.

We need to investigate the replacement(s) and to adapt our systems and scripts to it (noticeably, the Continuous Integration execution time database).

Associated revisions

Revision 5dac9945 (diff)
Added by Gianluca Petrillo about 4 years ago

Removed CPU time tracking during event display (issue #8131).

Apart from exceptional needs, CPU timing on a interactive job makes
little sense.

Revision 85277d93 (diff)
Added by Gianluca Petrillo about 4 years ago

Adding configuration for resource tracking services

This is related to issue #8131 and #8132.

History

#1 Updated by Lynn Garren over 5 years ago

  • Subject changed from Investigate the new TimeService replacements to Investigate the new Timing replacements
  • Status changed from New to Accepted

#2 Updated by Gianluca Petrillo over 5 years ago

My description above also contains a typo.
Just to reiterate, this is about Timing, the art service reporting how long modules take to run, and not TimeService, LArSoft's service providing information about when the event happened.

#3 Updated by Gianluca Petrillo about 4 years ago

  • Description updated (diff)
  • Category set to Other
  • Assignee set to Gianluca Petrillo
  • Estimated time set to 4.00 h

Fixed the typo in description when I figured out how.

#4 Updated by Gianluca Petrillo about 4 years ago

  • % Done changed from 0 to 80

Branch feature/gp_Issue8103 has been updated for repositories lardata, larevt, larsim, larreco, larana, lareventdisplay and larexamples.
The update consists of three types of interventions on FHiCL files configuring Timing, SimpleMemoryCheck or MemoryPeakReporter modules:

  1. configurations using service configuration bundles (e.g., @table::argoneut_services): the services mentioned above have been removed
  2. configurations not using service configuration bundles: the service configuration bundle standard_resourcetrackers has been added to the service configuration
  3. event display configuration: the service configuration has been removed, because in general this type of profiling information is not useful in interactive jobs

A new configuration file has been added in lardata: lardata/Utilities/resourcetracking_services.fcl, with standard configuration for MemoryTracker and TimeTracker services. This is written for the services as present in art 2.1 and newer (it will fail with art 2.0).

The recommendation is that the experiments add the tracking services in their service configuration bundles, so that they are executed in every job apart from the interactive ones.
This is as simple as including resourcetracking_services.fcl and adding @table::standard_resourcetrackers in your central service configuration.
This is the reason why this resolution just removed the resource tracking services from the many configuration files in category 2.

Edit: added larexamples.

#5 Updated by Gianluca Petrillo about 4 years ago

(branches will be pushed after LArSoft v06_03_00 is released)

#6 Updated by Gianluca Petrillo about 4 years ago

Feature branches have been updated to LArSoft v06_03_00 and pushed (larexamples was added to the list above).
The test with these branches excluded lariatsoft and dunetpc, which are not available yet for v06_03_00. Previously, they were tested under v06_02_00.

#7 Updated by Gianluca Petrillo about 4 years ago

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

#8 Updated by Gianluca Petrillo about 4 years ago

It turns out that there is no reason to withhold resourcetracking_services.fcl. So it is now available in develop branch of lardata for anybody willing to use it.

#9 Updated by Gianluca Petrillo about 4 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF