|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jira is not the site to use for what amounts to a support request. Please direct further questions to the jenkinsci-users mailing ist, or #jenkins on Freenode.
That said, you seem to be using the Maven project type very heavily. There are certain inefficiencies in that (and Matrix/multi-config projects) that cause loading of all (usually lazily loaded) builds. Coupled with the fact that Maven projects and builds have a disk footprint of 1+N freestyle projects/builds (N being the number of modules built), these are very resource (disk) intensive. Also, the Dashboard with its aggregate statistics forces loading of all builds. Get rid of that, or get a faster disk.
Some inefficiencies have been improved in more recent Jenkins versions, so upgrading may be worth a try.