|
||||||||
|
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/groups/opt_out.
Update
I just modified the configuration of my master slightly as follows:
And so far this seems to have alleviated the slow dashboard problem. Everything else remained unchanged in my configuration. All of the same builds previously running on the local machine are still running there, so the overall load on the system is consistent. The same version of Jenkins, with all the same plugins (and versions of those plugins) remain. etc.
This seems to suggest that there may be some kind of threading problem with the main Jenkins dashboard where if too may child threads are spawned for concurrently running builds something (Jenkins, the JVM, etc.) runs out of resources or something and thus the web dashboard gets blocked until sufficient resources (ie: threads) become available.