Are these single-file artifacts, or directory trees with lots of files in them? Archiving large numbers of files in a job makes Jenkins very, very slow. I worked around this by having my job create an archive itself of the artifacts, and then sending that archive to Jenkins to store. This means that reviewing the artifacts requires downloading and unpacking the archive file, but it made Jenkins run at a much more tolerable speed.
----- Original Message ----- From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Apr 12 2013 10:11:18 Yes, The artifacts for some jobs will be around 1GB(around 10% of the jobs) and for the remaining it will be around 500-600MB. There are nearly 150 jobs in the server. There are 16 slaves tied to the master, but not all the slaves share the load. Currently more than 80% of the jobs are processed by the master jenkins server only. We are trying to setup more slaves and share the load between master and slave, but got to fix the slowness of jenkins master first. -- View this message in context: http://jenkins.361315.n4.nabble.com/Slowness-in-Jenkins-tp4662449p4662561.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.
