Re: Performance issue of blue ocean with large job count

John, are you describing an issue for matrix jobs? We are tracking something like this in JENKINS-37104 On Fri, Aug 5, 2016 at 11:03 AM John D. Ament wrote: > Every module of every job gets included. At a minimum only the top > projects shoul

Re: Performance issue of blue ocean with large job count

Every module of every job gets included. At a minimum only the top projects should show up. Note that we do have plain old maven projects. John On Thu, Aug 4, 2016 at 7:38 PM James Dumay wrote: > Do you want to exclude non-pipeline jobs from the listing? If so what is > your motivation for do

Re: Performance issue of blue ocean with large job count

Do you want to exclude non-pipeline jobs from the listing? If so what is your motivation for doing so? On Fri, Aug 5, 2016 at 9:37 AM, John D. Ament wrote: > Sure, pagination will help. But can I also disable non-pipeline jobs? > > > On Thu, Aug 4, 2016 at 7:29 PM James Dumay wrote: > >> It re

Re: Performance issue of blue ocean with large job count

Sure, pagination will help. But can I also disable non-pipeline jobs? On Thu, Aug 4, 2016 at 7:29 PM James Dumay wrote: > It really is coming! Should be in next weeks alpha release :) > > > On Thursday, August 4, 2016 at 10:01:41 PM UTC+10, Daniel Beck wrote: > >> Pagination is currently being

Re: Performance issue of blue ocean with large job count

It really is coming! Should be in next weeks alpha release :) On Thursday, August 4, 2016 at 10:01:41 PM UTC+10, Daniel Beck wrote: > > Pagination is currently being worked on and should be done in a week or > two IIRC. I learned when I complained about the 100% CPU usage in some > views :-) >

Re: Performance issue of blue ocean with large job count

Pagination is currently being worked on and should be done in a week or two IIRC. I learned when I complained about the 100% CPU usage in some views :-) > On 28.07.2016, at 15:32, John D. Ament wrote: > > We have a large number of jobs in our jenkins. Very few of them are actual > pipelines t

Performance issue of blue ocean with large job count

We have a large number of jobs in our jenkins. Very few of them are actual pipelines though. Looking at blue ocean, it seems like it should only be picking up pipelines. The response to load the initial JSON is > 1 minute and is very slow to render. Is there any way to cut down the jobs bein