-
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
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Open
-
[JENKINS-49347] BlueOcean unusably slow, maybe related to having a lot of builds stored in history
| Link |
New:
This issue duplicates |
| Link |
New:
This issue duplicates |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Attachment | New: pipeline-BO-loadtimes-console.png [ 41519 ] | |
| Attachment | New: pipeline-BO-loadtimes.7z [ 41520 ] | |
| Attachment | New: pipeline-BO-loadtimes.png [ 41521 ] |
| Attachment | New: support_2018-02-19_12.57.04.zip [ 41522 ] |
| Assignee | New: Vivek Pandey [ vivek ] | |
| Resolution | Original: Duplicate [ 3 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
| Epic Link | New: JENKINS-37957 [ 174099 ] |
| Sprint | New: Blue Ocean 1.5 - beta 1 [ 456 ] |
| Sprint | Original: Blue Ocean 1.5 - beta 1 [ 456 ] | New: Blue Ocean 1.5 - beta 2 [ 481 ] |
| Rank | New: Ranked lower |