|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I did not mean to discourage you from reporting issues. In my experience however there's often little (or only much delayed) response to JIRA issue reports, and this looked more like a request for timely help to me. Therefore the suggestion to discuss this on the list, which also facilitates the conversation when additional information is needed. If it turns out it's an issue with a clear(ish) solution, it can always be filed and tracked then.
I suggest you get rid of the Dashboard modules that require loading all builds (e.g. the success/unstable/failure stats), or prune your projects with large numbers of builds (the more Maven modules, the fewer builds to retain). When Jenkins is forced to load a large number of files (e.g. N builds of a project consisting of M modules each is N*M files), performance suffers as a result of architectural choices (accessible hierarchical file system storage, XML file per item/build, lazy "on demand" loading of build records since 1.48x).