|
||||||||
|
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.
Just some insight for this issue:
We had profiled jenkins during our slow startup and found that what was really taking a long time was reading all the builds.
To work around the problem, we did an exhaustive cleanup and setup a very aggressive policy to clean up old builds (only a few selected jobs keep a longer history).
We were able to reduce the startup time from 80min to 5 minutes.
Other things that help: because the problem is due to intensive I/O reading every build file, improving the hardware also helps to alleviate the problem.