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

Very slow dashboard and /search response in some cases (slowing dashboard load)

    Details

    • Epic Link:
    • Sprint:
      Blue Ocean 1.0-rc4
    • Similar Issues:

      Description

      User has reported a performance problem on 1.0-rc3 loading the dashboard.

      It appears from a brief analysis of their HAR file – attached here – that /blue/pipelines takes 33 seconds to load and search taking 30s or so: 

      JENKINSDOMAIN/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26. The response is about the normal size expected (perhaps slightly larger, but not large enough to explain the load time, content can be seen in the har file).

       

       

       

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment - - edited

            Hans Schulz please open a new issue and email me a HAR file for the page load at jdumay@cloudbees.com

            If you are a CloudBees customer you will get a better turn around by filing a ticket at support.cloudbees.com and attaching a the HAR file there.

            Show
            jamesdumay James Dumay added a comment - - edited Hans Schulz please open a new issue and email me a HAR file for the page load at jdumay@cloudbees.com If you are a CloudBees customer you will get a better turn around by filing a ticket at support.cloudbees.com and attaching a the HAR file there.
            Hide
            michaelneale Michael Neale added a comment -

            Hans Schulz it would be better to open a fresh ticket than re-open this one with all the noise as this isn't related to config history plugin (likey another plugin, or number of favourites, could be a lot of things).

            Then can chase it down. 

            Show
            michaelneale Michael Neale added a comment - Hans Schulz it would be better to open a fresh ticket than re-open this one with all the noise as this isn't related to config history plugin (likey another plugin, or number of favourites, could be a lot of things). Then can chase it down. 
            Hide
            schulzha Hans Schulz added a comment - - edited

            Repoening because the issue is not fixed.

            As Marley Kudiabor wrote, the config history plugin did not cause the long loading times.

            I am experiencing the exact same issue, opening blue ocean takes 18 seconds for us on a very fast server. Deleting the config history did not help.

            I've noticed that the dashboard loads quickly when I'm not authenticated.

            Jenkins version 2.46.3, BlueOcean 1.1.2

            Show
            schulzha Hans Schulz added a comment - - edited Repoening because the issue is not fixed. As Marley Kudiabor wrote, the config history plugin did not cause the long loading times. I am experiencing the exact same issue, opening blue ocean takes 18 seconds for us on a very fast server. Deleting the config history did not help. I've noticed that the dashboard loads quickly when I'm not authenticated. Jenkins version 2.46.3, BlueOcean 1.1.2
            Hide
            kudiaborm Marley Kudiabor added a comment - - edited

            Modified path in description to remove our jenkins domain from google search results

            Show
            kudiaborm Marley Kudiabor added a comment - - edited Modified path in description to remove our jenkins domain from google search results
            Hide
            michaelneale Michael Neale added a comment -

            The job config history plugin is infamous for introducing problems in various places (unless you use ramdisk, rarely save changes to config), so this isn't too surprising. 

            If you dont' want to remove it (you probably have it for a reason), then there will be a fix coming, and blue ocean shouldn't be slowed down by this either. 

            The fix in summary: 

            • don't just fetch everything about a pipeline just in case it is needed 
            • don't return history data that isn't wanted anyway

            One of these should land soon (one is a longer term, one is a shorter term enhancement).

             

            Thanks! 

             

            Show
            michaelneale Michael Neale added a comment - The job config history plugin is infamous for introducing problems in various places (unless you use ramdisk, rarely save changes to config), so this isn't too surprising.  If you dont' want to remove it (you probably have it for a reason), then there will be a fix coming, and blue ocean shouldn't be slowed down by this either.  The fix in summary:  don't just fetch everything about a pipeline just in case it is needed  don't return history data that isn't wanted anyway One of these should land soon (one is a longer term, one is a shorter term enhancement).   Thanks!   

              People

              • Assignee:
                vivek Vivek Pandey
                Reporter:
                jamesdumay James Dumay
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: