-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: 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?
- duplicates
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Open
-