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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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
          Jim Klimov
        2. pipeline-BO-loadtimes.png
          112 kB
          Jim Klimov
        3. pipeline-BO-loadtimes-console.png
          79 kB
          Jim Klimov

            Assignee:
            Vivek Pandey
            Reporter:
            Jim Klimov
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: