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

BlueOcean unusably slow, maybe related to having a lot of builds stored in history

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • blueocean-plugin
    • None
    • Blue Ocean 1.5 - beta 3

      During FOSDEM discussion about a problem we had with BlueOcean being prohibitively slow, a reasonable guess from markwaite was that our system in question stores a long history of builds - tens of thousands of those. Indeed, when the browser sends a request for BlueOcean (main panel, particular project, a build) the server spends a lot of time (minutes) in "wait" state for one of the CPU cores while others are idle or in small user time spending.

      Rendering the list of recent 50-100 builds or details of a particular build should not require inspecting all histories of all builds, right?

        1. pipeline-BO-loadtimes.7z
          1.57 MB
        2. pipeline-BO-loadtimes.png
          pipeline-BO-loadtimes.png
          112 kB
        3. pipeline-BO-loadtimes-console.png
          pipeline-BO-loadtimes-console.png
          79 kB
        4. support_2018-02-19_12.57.04.zip
          1.14 MB

            vivek Vivek Pandey
            jimklimov Jim Klimov
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: