Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47007

Excessive CPU usage on pipeline "Stage View"

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins 2.78
      Pipeline Stage View Plugin 2.9
      Chrome 60.0.3112.113
      macOS 10.12.6
    • Similar Issues:

      Description

      The pipeline plugin's "Stage View" takes more than 100% of a single CPU just to keep it open in the browser.

      The only thing on the screen which appears to be moving is the progress bar, so I'm assuming it is the cause of the problem. Perhaps it's being repainted too frequently?

       

        Attachments

          Activity

          Hide
          jaredxu Jared Xu added a comment -

          I also came across this problem recently. After using pipeline jobs for a while, the CPU usage soars to extremely high level(200%) and cannot recover even stop using it.

          Show
          jaredxu Jared Xu added a comment - I also came across this problem recently. After using pipeline jobs for a while, the CPU usage soars to extremely high level(200%) and cannot recover even stop using it.
          Hide
          trejkaz trejkaz added a comment -

          For me it recovers after I close the tab, but while the tab is open, forget about doing any other operation on the computer which requires the graphics card...

          Show
          trejkaz trejkaz added a comment - For me it recovers after I close the tab, but while the tab is open, forget about doing any other operation on the computer which requires the graphics card...
          Hide
          mdebord1 Matt Dee added a comment -

          It's 2019, Jenkins is on 2.190.x and Stage View is still rocketing CPU usage after being on the page for a few minutes. Need to constantly close tab and re-open in a new one to keep resource utilization manageable. 

          Show
          mdebord1 Matt Dee added a comment - It's 2019, Jenkins is on 2.190.x and Stage View is still rocketing CPU usage after being on the page for a few minutes. Need to constantly close tab and re-open in a new one to keep resource utilization manageable. 
          Hide
          josealavez Jose Carlos Alavez Gonzalez added a comment -

          For anyone looking at this issue: Collapsing the Build History with the minus sign close to the Trends label made my CPU to go fine again.

          Show
          josealavez Jose Carlos Alavez Gonzalez added a comment - For anyone looking at this issue: Collapsing the Build History with the minus sign – close to the Trends label made my CPU to go fine again.
          Hide
          brdloush_ Tomas Brejla added a comment - - edited

          My observation is that the animated progress bars (striped) were consuming a ton of CPU time on my machine. The more running pipelines, the more animated progress bars - and therefore the more wasted CPU time.

          I managed to improve this dramatically by overriding CSS (there are browser plugins which allow you to define per-site CSS overrides):

           

          .cbwf-widget .progress-bar.active

          { animation: none; -webkit-animation: none; -o-animation: none; }

           

          Suddenly the CPU usage of the tab with Stage View dropped from 100-200% to 0% with occasional short 40% spike, which seems to happen every 3-5 seconds and seems to be a result of page DOM reload/replacement.

           

          Show
          brdloush_ Tomas Brejla added a comment - - edited My observation is that the animated progress bars (striped) were consuming a ton of CPU time on my machine. The more running pipelines, the more animated progress bars - and therefore the more wasted CPU time. I managed to improve this dramatically by overriding CSS (there are browser plugins which allow you to define per-site CSS overrides):   .cbwf-widget .progress-bar.active { animation: none; -webkit-animation: none; -o-animation: none; }   Suddenly the CPU usage of the tab with Stage View dropped from 100-200% to 0% with occasional short 40% spike, which seems to happen every 3-5 seconds and seems to be a result of page DOM reload/replacement.  

            People

            • Assignee:
              svanoort Sam Van Oort
              Reporter:
              trejkaz trejkaz
            • Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated: