Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ctrl_bps
-
Epic Link:
-
Team:Data Facility
-
Urgent?:No
Description
Quentin Le Boulc'h reported on Slack that some of the timings ctrl_bps displays during a submission are cumulative instead showing how long it took to perform a given step. Below is the example log output he provided:
lsst.ctrl.bps.pre_transform INFO: Creating quantum graph took 5808.56 seconds |
lsst.ctrl.bps.pre_transform INFO: Reading quantum graph (/sps/lsst/users/leboulch/bps/submit/HSC/runs/RC2/w_2021_41/step1/20211013T124311Z/HSC_runs_RC2_w_2021_41_step1_20211013T124311Z.qgraph)
|
lsst.ctrl.bps.pre_transform INFO: Reading quantum graph with 208060 nodes took 265.33 seconds |
lsst.ctrl.bps.drivers INFO: Run QuantumGraph file /sps/lsst/users/leboulch/bps/submit/HSC/runs/RC2/w_2021_41/step1/20211013T124311Z/HSC_runs_RC2_w_2021_41_step1_20211013T124311Z.qgraph
|
lsst.ctrl.bps.drivers INFO: Acquiring QuantumGraph took 6075.50 seconds |
lsst.ctrl.bps.drivers INFO: Clustering quanta
|
lsst.ctrl.bps.drivers INFO: Clustering quanta took 6169.88 seconds |
Missed timing the submit stage. Otherwise looks good and can merge.