If you're using the warnings plugin, I believe it was known (at least for some versions of the warnings plugin) that warnings processing time increases at a greater than linear rate as the length of the log increases.
http://jenkins.361315.n4.nabble.com/Has-warnings-plugin-become-CPU-intensive-td963935.html is a mailing list thread from 2009 which may give some hints as possible ideas you could test to see if you can isolate the specific case that is causing your issue. Mark Waite >________________________________ > From: Anthony Newnam <anth...@bnovc.com> >To: jenkinsci-users@googlegroups.com >Sent: Tuesday, May 22, 2012 1:57 PM >Subject: long output = slow build times > > >I believe that with some of my compile jobs that have large output (~50MB) of >data, it causes them to be much slower. I haven't measured this exactly to >find the cause, but it seems like there is a strong correlation. > >Have other seen this behavior or are there any optimizations available for it? >Does Jenkins send the logs compressed between the nodes? > >I'm using Jenkins 1.441. > >Thanks > > >
