[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history

jdumay@cloudbees.com (JIRA)

unread,

Feb 18, 2018, 7:25:02 PM2/18/18

to jenkinsc...@googlegroups.com

James Dumay resolved as Duplicate

Jim Klimov Ill close this against the issues quoted by Vivek Pandey (likely to be the cause).

However, would be great to capture a HAR file of specific page loads and capture a support bundle to help us diagnose these problems. We know there are optimizations to be make but we need specific info

Jenkins /

JENKINS-49347

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

Change By:	James Dumay
Status:	Open Resolved
Resolution:	Duplicate

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

jimklimov@gmail.com (JIRA)

unread,

Feb 19, 2018, 7:54:02 AM2/19/18

to jenkinsc...@googlegroups.com

Jim Klimov commented on

JENKINS-49347

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

Added HAR and respective screenshots (console is rather empty and uninteresting, but load times are spectacular).

Add Comment

jimklimov@gmail.com (JIRA)

unread,

Feb 19, 2018, 7:54:02 AM2/19/18

to jenkinsc...@googlegroups.com

Jim Klimov updated an issue

Jenkins /

JENKINS-49347

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

Change By:	Jim Klimov
Attachment:	pipeline-BO-loadtimes-console.png
Attachment:	pipeline-BO-loadtimes.7z
Attachment:	pipeline-BO-loadtimes.png

Add Comment

jimklimov@gmail.com (JIRA)

unread,

Feb 19, 2018, 8:15:02 AM2/19/18

to jenkinsc...@googlegroups.com

Jim Klimov updated an issue

Jenkins /

JENKINS-49347

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

Change By:	Jim Klimov
Attachment:	support_2018-02-19_12.57.04.zip

Add Comment

jimklimov@gmail.com (JIRA)

unread,

Feb 19, 2018, 8:34:02 AM2/19/18

to jenkinsc...@googlegroups.com

Jim Klimov edited a comment on

JENKINS-49347

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

Added HAR and respective screenshots (console is rather empty and uninteresting, but load times are spectacular).

UPDATE: Added somewhat redacted support data.

Statistics-wise, at the moment there are about 40k builds stored in history (and yes, much of the time spent in rendering BO can be Java walking the filesystem to find and parse all that build data):

````
[root@jenkins2 jenkins/jobs]# sync; echo 3 > /proc/sys/vm/drop_caches
[root@jenkins2 jenkins/jobs]# find . -name build.xml | wc -l
39847

real    12m40.689s
user    0m12.259s
sys     0m36.710s
````

and 94 known "users" (many of which were auto-registered from upstream/3rd party projects' commits that were built here; about 20 actual internal users). Listing `$JENKINS_URL/view/Masters/asynchPeople/` or going into the active users and listing builds they are associated with at `$JENKINS_URL/user/myusername/builds` also takes several minutes, at least first time after a filesystem cache flush for cleaner results (and comparably long with a "dirty" cache too).

The system is a KVM VM, has 4Gb RAM assigned and about 1.3Gb of that is free. I'll try bumping it to 8Gb so more FS (meta)data can be cached, at least...

Add Comment

jimklimov@gmail.com (JIRA)

unread,

Feb 19, 2018, 8:35:02 AM2/19/18

to jenkinsc...@googlegroups.com

Jim Klimov edited a comment on

JENKINS-49347

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

Added HAR and respective screenshots (console is rather empty and uninteresting, but load times are spectacular).

UPDATE: Added somewhat redacted support data.

Statistics-wise, at the moment there are about 40k builds stored in history (and yes, much of the time spent in rendering BO can be Java walking the filesystem to find and parse all that build data):

```` {noformat}

[root@jenkins2 jenkins/jobs]# sync; echo 3 > /proc/sys/vm/drop_caches
[root@jenkins2 jenkins/jobs]# find . -name build.xml | wc -l
39847

real    12m40.689s
user    0m12.259s
sys     0m36.710s

```` {noformat}

and 94 known "users" (many of which were auto-registered from upstream/3rd party projects' commits that were built here; about 20 actual internal users). Listing

` {{ $JENKINS_URL/view/Masters/asynchPeople/ ` }} or going into the active users and listing builds they are associated with at ` {{ $JENKINS_URL/user/myusername/builds ` }} also takes several minutes, at least first time after a filesystem cache flush for cleaner results (and comparably long with a "dirty" cache too).

The system is a KVM VM, has 4Gb RAM assigned and about 1.3Gb of that is free. I'll try bumping it to 8Gb so more FS (meta)data can be cached, at least...