Recently we have found our Jenkins getting slower and slower.

   * Clicking on a job to see the history is slow as it 
   * Navigating  to the main page. 

By slow I mean it can take 30 to 120 or so seconds. 

We have 25 jobs with numbers of builds ranging from 10 or so to at most 
1756. 

Most of these are maven builds which have inside them 67 modules. 

Having read many posts and other stuff here and on the web in general I 
thought that removing old builds may speed things up. 

I also noticed that when using JavaMelody much time is spent doing 
java.io.UnixFileSystem.getBooleanAttributes0(Native Method) 

Using the discard old build function to keep 30 builds didn't delete old 
build so on some of the jobs I manually purged  the old builds from 
job/builds and job/modules/**/builds. 

On the jobs I did this to it didn't seem to speed it up. 

I also found that clicking on jobs with very little build history, for 
instance 8 was slower than the one with 1756, which doesn't seem to make 
sense. 

So, should the changing the value to builds to keep to 30 have deleted the 
old ones? If so why didn't it and what can I do to fix it?

Is there something else that can be done to improve the performance?

Thanks in advance,

Ian

-- 
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.


Reply via email to