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

The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins 1.510 + gerrit 2.5.2 on Ubuntu 12.04. See attached systeminfo file for details as reported by Jenkins.
    • Similar Issues:

      Description

      I just updated from Jenkins 1.505 today as part of resolving another outstanding issue. I notice that the main dashboard page is much slower to load than it was before, and also notice that the server gets high CPU load in the process (it gets super-bad if you try and reload it a few times, as one might do when a page seems frozen). This is not the case on the individual job pages, the "manage Jenkins" page or other such ancillary pages.

      My main page has quite a few jobs in the main view, but that didn't have an adverse effect before.

      It did have some trouble connecting to the slave, right after the update, but that appears to be working properly now.

      At the moment, several minutes after it seemed to have normalized a bit, I see one CPU is now completely spiked by Jenkins.

      Downgraded to 1.505 + git-client 1.03 until this is resolved or explained.

      Note 1: After the downgrade things are back to being speedy. The dashboard loads quickly on opening it or on switching to it, and any CPU load is very brief (versus waiting several seconds for the page to display, or much longer if it was refreshed a few times). I hit reload several times in succession... it was reloaded in a second with no major load on the CPU (versus waiting around 30 seconds for the page to finally appear on the newer version).

      Note 2: Even in 1.505 you end up with one Jenkins-bearing CPU that stubbornly spikes at 100% after a few quick reloads... and appears to stay that way (if you reload a few more times you still end up with this condition, though it might be on another CPU in the system). So the persistent CPU spike may or may not be related to this issue.

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            Note that dashboard-view 2.8 includes a fix for JENKINS-15858; it is unclear whether or not this bug is a duplicate.

            Show
            jglick Jesse Glick added a comment - Note that dashboard-view 2.8 includes a fix for JENKINS-15858 ; it is unclear whether or not this bug is a duplicate.
            Hide
            martymacgyver Martin Falatic added a comment -

            15858 seems to involve much earlier versions of Jenkins as well, where I've never encountered the problem. Jenkins 1.505 is the last stable release from my perspective... and that's assuming this was the only new showstopper introduced since then that remains outstanding (thankfully jgit as a default was removed quickly).

            Show
            martymacgyver Martin Falatic added a comment - 15858 seems to involve much earlier versions of Jenkins as well, where I've never encountered the problem. Jenkins 1.505 is the last stable release from my perspective... and that's assuming this was the only new showstopper introduced since then that remains outstanding (thankfully jgit as a default was removed quickly).
            Hide
            mambu Marco Ambu added a comment -

            The default job page in Jenkins is not the dashboard view plugin page.
            The dashboard-view is a plugin and must be installed and configured.
            Removed dashboard-view from the components.

            Show
            mambu Marco Ambu added a comment - The default job page in Jenkins is not the dashboard view plugin page. The dashboard-view is a plugin and must be installed and configured. Removed dashboard-view from the components.
            Hide
            jglick Jesse Glick added a comment -

            JNR in 1.518+ ought to help, given the reported thread dumps.

            Show
            jglick Jesse Glick added a comment - JNR in 1.518+ ought to help, given the reported thread dumps.
            Hide
            feystorm Patrick Hemmer added a comment -

            Experienced this same issue with the LTS 1.509.1 release on Ubuntu LTS 12.04.
            Upgrading to openjdk-7 resolved this issue for me. Was experiencing the exact same `JavaPOSIX.readlink` thing.
            I wanted to stay on the LTS release, and not have to upgrade to 1.518+. So just providing this info for anyone else who is looking for the same.

            Show
            feystorm Patrick Hemmer added a comment - Experienced this same issue with the LTS 1.509.1 release on Ubuntu LTS 12.04. Upgrading to openjdk-7 resolved this issue for me. Was experiencing the exact same `JavaPOSIX.readlink` thing. I wanted to stay on the LTS release, and not have to upgrade to 1.518+. So just providing this info for anyone else who is looking for the same.

              People

              • Assignee:
                Unassigned
                Reporter:
                martymacgyver Martin Falatic
              • Votes:
                5 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: