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

Create Gen 2 vs. Gen 3 comparison dashboard

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ap_verify, squash
    • Labels:
      None

      Description

      Following DM-28888 (and subsequent bugfixes) we now have both Gen 2 and Gen 3 ap_verify runs in SQuaSH. The existing dashboards are designed for investigating a single run at a time. Create a new dashboard that compares Gen 2 and Gen 3 directly, in order to keep the existing boards from having confusing mixes of plots and to make it easy to remove the comparisons once we've dropped Gen 2.

      Plots on the new dashboard should probably focus on performance, and on metrics that are known to be robust to processing order (since even what is meant by "processing order" is very different in Gen 2 and Gen 3).

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-28888 Allow SQuaSH uploads from ap_verify Gen 3

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-12549 ap_pipe must call AssociationTask in a reproducible order

          • Done
          mentioned in

          Page Loading...

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            krzys Krzysztof Findeisen added a comment - - edited

            "Final" version of the dashboard is available at https://chronograf-demo.lsst.codes/sources/2/dashboards/73. I've left out the memory usage metric, since it's not clear what that's actually measuring in Gen 3; I'll ask Middleware about it on Monday.

            While working on this ticket I also noticed that our timing metrics were profiling AssociationTask rather than DiaPipelineTask, so I've fixed that on the "AP runtime metrics" dashboard.

            Show
            krzys Krzysztof Findeisen added a comment - - edited "Final" version of the dashboard is available at https://chronograf-demo.lsst.codes/sources/2/dashboards/73 . I've left out the memory usage metric, since it's not clear what that's actually measuring in Gen 3; I'll ask Middleware about it on Monday. While working on this ticket I also noticed that our timing metrics were profiling AssociationTask rather than DiaPipelineTask , so I've fixed that on the "AP runtime metrics" dashboard.
            Hide
            Permalink
            ebellm Eric Bellm added a comment -

            Great work Krzysztof Findeisen!

            Show
            ebellm Eric Bellm added a comment - Great work Krzysztof Findeisen !

              People

              Assignee:
              krzys Krzysztof Findeisen
              Reporter:
              krzys Krzysztof Findeisen
              Reviewers:
              Eric Bellm
              Watchers:
              Eric Bellm, Krzysztof Findeisen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.