Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-2419

SPIKE - Research DLPS process with a view to reducing the CPU utilization

    Details

    • Sprint:
      CFAMX 2019R2 Sprint 4
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      2
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As a product owner i want you (the developer) to review the DLPS generation process that runs at 00:00 each night with a view to optimizing the CPU usage of this process

      Notes

      • Currently the DLPS and Forecast Import processes compete for the same CPU resources
      • Scheduled Task
      • Service Method Task

      Acceptance Criteria

      1. Confirm that stories are written that document the testable changes needed to improve the CPU utilization of the DLPS generation job

        Attachments

        1. DLPS_SMT.png
          3 kB
          Will Englefield
        2. DLPS.png
          10 kB
          Will Englefield

          Issue Links

          implements

          Feature Request - CFAMX-2410 Support rollout of Forecast Import

          • Major - Major loss of function.
          • Closed

            Activity

              People

              • Assignee:
                Michael.DeBinder Michael DeBinder (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 14h
                  14h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 7.5h Time Not Required
                  7.5h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.