-
Bug
-
Resolution: Fixed
-
Major
-
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?
- duplicates
-
JENKINS-44995 Very slow activity/pipeline screen load (often when logged in)
-
- Closed
-
-
JENKINS-48868 blue ocean dashboard taking more than 50s to load.
-
- Closed
-
- is related to
-
JENKINS-63481 Blue ocean pipeline activity load is very slow
-
- Open
-
There were few underlying issues. One being related to how favorites were rendered (affects logged in user with long build history) and the other had to do with unnecessary and expensive data returned as part of latestRun field.
Fix is in review stage and should be merged soon. See https://github.com/jenkinsci/blueocean-plugin/pull/1638 and https://github.com/jenkinsci/blueocean-plugin/pull/1635.