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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
