Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-32217

BPS displays cumulative timings instead of time intervals during a submission

    XMLWordPrintable

    Details

      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

        Attachments

          Activity

          Hide
          mgower Michelle Gower added a comment -

          Missed timing the submit stage. Otherwise looks good and can merge.

          Show
          mgower Michelle Gower added a comment - Missed timing the submit stage. Otherwise looks good and can merge.
          Hide
          yusra Yusra AlSayyad added a comment - - edited

          Hi Mikolaj Kowalik your backport request has been approved, and we have some instructions for how to backport this to v23.0.x here: https://developer.lsst.io/v/DM-32357/work/backports.html

          You have a couple options:
          1) Follow the instructions to backport it yourself (and ask for clarification if they're confusing, since you'd be the first person other than the author to follow them. I'll incorporate your suggestions into the guide) or
          2) Ask one of the DP0.2 release managers (which is me right now) to backport it.

          We are planning on building v23.0.0.rc2 on Thursday 12pm PDT. This doesn't have to be backported by then; there will be an rc3 run a week or two after.

          Show
          yusra Yusra AlSayyad added a comment - - edited Hi Mikolaj Kowalik your backport request has been approved, and we have some instructions for how to backport this to v23.0.x here: https://developer.lsst.io/v/DM-32357/work/backports.html You have a couple options: 1) Follow the instructions to backport it yourself (and ask for clarification if they're confusing, since you'd be the first person other than the author to follow them. I'll incorporate your suggestions into the guide) or 2) Ask one of the DP0.2 release managers (which is me right now) to backport it. We are planning on building v23.0.0.rc2 on Thursday 12pm PDT. This doesn't have to be backported by then; there will be an rc3 run a week or two after.

            People

            Assignee:
            mkowalik Mikolaj Kowalik
            Reporter:
            mkowalik Mikolaj Kowalik
            Reviewers:
            Michelle Gower
            Watchers:
            Michelle Gower, Mikolaj Kowalik, Yusra AlSayyad
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.