my problem is back. It was not related to plugin. --pawel
On Thursday, January 17, 2013 10:22:13 AM UTC+1, Pawel Jasinski wrote: > > hi, > > I am in the middle of similar exercise. 1.480.1 on windows 7-64. > My symptoms matched description here: > > http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-15601-Main-dashboard-takes-minutes-to-load-in-browser-td4644096.html > > > To enable access log: > http://jenkins.361315.n4.nabble.com/How-to-enable-access-log-td4629088.html > > There is also a simple technique to observe details of sluggish/stuck > responses. In Firefox, open Tools->Web Developer->Web Console. Now if you > hit the reload you will see individual response time for each individual > page element. I have seen a lot of things with response time under 500ms. > But some static elements with response time of 10+, 20+ or 30+ seconds. The > pages were stuck, on some pages images were missing. > > As a test, you can also use wget to hit the front page: > > wget -q -E -H -k -K -p -e robots=off http://your-jenkins-host:8080/ > > but wget does serialize everything, so it is not 100% equivalent of what > browser does. > > > For now, in my case the problem disappeared. The last thing I did was to > disable next-executions plugin. > > Cheers, > Pawel > > > > > On Thu, Jan 17, 2013 at 9:51 AM, Yitzhak Zuriel wrote: > >> We recently upgraded our Jenkins CI servers to the latest LTS version >> (4.480.1 -- before this we were using version 4.447.2) After this upgrade, >> we found that on our busiest servers (especially on a master of 8 slaves; >> all run on Windows Server 2008 r2) that the http response becomes very >> slow. It's inconsistent, but approximately half of the time the GUI >> responds either sluggishly or seems stuck. Has anyone experienced this? >> Does anyone have suggestions for how we can investigate the cause of this? >> We thought it might be due to intensive SCM polling activity of many >> projects' commit jobs, so we increased the polling intervals and spread >> them out more, and this had no effect. I'd appreciate any ideas. A small >> related question: one of the things we want to do for our investigation is >> to record logs of http activity. Which logger name(s) should we use to >> capture such logs? > > >
