|
||||||||
|
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.
After an upgrade of Jenkins v1.565.1 my startup time dropped down to about 30-40 min from the original 2 hours.
However, the startup is still long. In my case it is definitely due to the matrix plugin. After a few exchanges on the mailing lists the conclusion is that this is an I/O bottleneck due to Jenkins being sensitive to I/O operation rate. Others have mention a significant improvement when moving the build logs to solid state disks that can perform orders of magnitude more I/O ops per second.
I think to fix this situation one would need to rethink how Jenkins deals with I/O down to the core.