There are two directions : - increase the heap, that will allow Jenkins to keep more jobs/builds in memory (but this is not guaranteed) - try to remove some columns that may trigger useless load of all builds for a job
Vincent 2014/1/15 dennys <dennys.hs...@gmail.com> > I have hundred jobs and use view to separate them. Each view has 50~100 > jobs. > When I login one view, it takes about 10 seconds to show the page. > But I I click refreash, it only takes less than 1 second. > > And if I don't use Jenkins for a while, when I click it again, it takes 10 > seconds again. > I guess the reason is Jenkins need time to read every job and it's build > status. > > And since 2nd time is fast, I guessJenkins has a cache mechanism. > Is it possible to keep the cache in memory then we can have good user > response? > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/Page-load-slow-at-1st-time-but-fast-in-2nd-time-tp4687583.html > Sent from the Jenkins users mailing list archive at Nabble.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
