No, I'm not using that plugin. Thanks for pointing out a possible cause for my problems.
- David On Sunday, October 21, 2012 5:45:06 PM UTC+2, Baptiste Mathus wrote: > > Hi, > Just a small guess: are you using nested view plugin? > > If so, it might alternatively be related to another problem introduced > recently in the nested-view plugin (see recent archives about that, thread > started by mpapo). Btw, it's been fixed since we logged the issue. > > My 2 cents. > > Cheers > Le 21 oct. 2012 13:27, "David Resnick" <[email protected] <javascript:>> > a écrit : > >> Right, I'm also guessing that this is related to the lazy loading that >> was added in 1.485. >> >> Unfortunately, the long loading times are fairly consistent; the 5 minute >> time I mentioned was not the first time I loaded the main dashboard. In any >> case, while I expect lazy loading of builds to increase first time page >> load times I don't think that such a long load time for a page would be >> acceptable to any user of Jenkins. >> >> - David >> >> On Sunday, October 21, 2012 12:38:55 PM UTC+2, Richard Mortimer wrote: >>> >>> On 21/10/2012 10:52, David Resnick wrote: >>> > Since upgrading to 1.486 I've noticed long load times for some views >>> on >>> > our Jenkins instance. Longest load times are for the main dashboard >>> > (which includes over 100 jobs and thousands of builds) -- I just timed >>> 4 >>> > minutes 45 seconds for the page to load. Note that all pages do load >>> > eventually. >>> > >>> > Has anyone else encountered this regression? >>> Not specifically but it could be due to the lazy loading of build >>> information that was introduced in 1.485. I guess that is the flip side >>> of having faster startup times. Does a second load of the page work >>> quicker? >>> >>> That might be some useful feedback to provide to >>> [email protected] if it is causing problems. >>> >>> Regards >>> >>> Richard >>> >>> > >>> > - David >>> >>
