Just to let you know: we found it! It was the build-node-column plugin. https://issues.jenkins-ci.org/browse/JENKINS-21870
If I understand the source right, the plugin asks for every row in a view every slave for for all builds on that node until it has found the node which built the last build. Sounds very expensive to me if I think about the time it needs to render the build history of a node. BR and thanks for helping out.... Dirk 2014-02-18 13:01 GMT+01:00 Dirk Kuypers <[email protected]>: > Thanks for your comments. > > Searching for Functions.getRelativeLinkTo(Item) leads me to > > *https://issues.jenkins-ci.org/browse/JENKINS-18364 > <https://issues.jenkins-ci.org/browse/JENKINS-18364>* > No votes except mine so far.:-/ > > Regarding the number of jobs: Views containing 10 Jobs take 5-10 seconds > to load, views containing several hundred jobs take 10-20 seconds to load. > If there is nothing to see in a view because of user permissions the view > pops up in less than a second. > > Reconfiguring one of the global views takes about 20 minutes. Persisting > the global config.xml seems to be very costly with lots of jobs (and views). > > We tried using visualvm but as we are in a .NET development environment > with no luck. We were not able to attach to the process or did not get it > what to do.... > > BR > Dirk > > > > > > 2014-02-18 10:03 GMT+01:00 Daniel Beck <[email protected]>: > > /threadDump will tell you what the threads are doing. Look for 'Handling >> GET'. >> >> If you have large views (i.e. 500+ items actually shown), my guess is >> Functions.getRelativeLinkTo(Item), which iterates over all items in the >> view (requiring recomputation of what actually is part of the view) for >> every item to be shown. >> >> Another option could be expensive columns like 'Project Statistics >> Plugin' that require loading all builds from disk; or Maven Plugin jobs >> which have more builds than you think (see discussion in JENKINS-21487). >> >> On 18.02.2014, at 09:49, Dirk Kuypers <[email protected]> wrote: >> >> > Hi all, >> > >> > we have a quite big Jenkins installation (although I know from some >> posts to this lists that there are much bigger ones out there). A master >> which is only doing the web front-end with about 20 Slaves. We have a lot >> of jobs, at the moment about 3000 (job-dsl plugin rules;-) but in the end >> it could be 6000. >> > >> > Our problem is that selecting a global view takes around 20 seconds. >> Reconfiguring and saving a global view took about 20 minutes yesterday. >> > >> > Some things I observed: I think it has something to do with the number >> of global views (times number of jobs). My personal view is quite >> responsive, the global view contains about 20 views right now. Is it >> possible that Jenkins somehow has to iterate through all views to add a row >> to a view? I am wondering what could keep a 2.9 GHz CPU spinning at 100 % >> for 20 minutes. You could compute quite some fancy stuff in that time.;-) I >> do not see big IO-spikes, so (almost) everything seems to happen in memory. >> > >> > The server is an ESX instance with dual Xeon 2.9Ghz, disks are located >> on a 15 k SAS array, RAM allocated to the machine is 8 GByte at the moment. >> Jenkins version is 1.551, all used plugins are also latest versions. >> > >> > Some hints where to look at? Are there some plugins known which slow >> down everything if you have a large number of jobs? >> > >> > Thanks >> > Dirk >> > >> > -- >> > 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 [email protected]. >> > 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 [email protected]. >> 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
