![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
build-node-column, core |
|
Created:
|
19/Feb/14 10:56 AM
|
|
Description:
|
With increasing number of slaves the performance of the build node column display seems to decrease significantly.
In our setup, after increasing number of Slave from 7 to 18, all views that are showing the "Last Build Node" column took more than double time to show.
For example a view containing approximately 70 jobs took about 15 seconds to show with 7 slaves and 55 seconds with 18 slaves.
Monitoring the CPU load (Prcoess Explorer and Jenkins Melody Monitor Plugin) shows a fully loaded CPU-core for the request.
After completely removing the "Last Build Node" column, the same view appears in less than a second.
The number of jobs obviously also has an impact (i.e. a view with 20 jobs and "Last Build Node" column shows in about 5 seconds). But the impact of the number of Slaves seems to be much higher.
I didn't test if the number of Offline versuse Online slaves has an impact.
|
|
Environment:
|
Jenkins v 1.551 on JRE 1.7.51 64 bit on Windows Server 2008 R2 64bit.
All Plugins are lates versions.
That is: Build-Node-Column Plugin v 0.1
And just in case it is related:
Sectioned View Plugin v 1.18
DropDownViewsTabbar v 1.6
|
|
Project:
|
Jenkins
|
|
Labels:
|
performance
plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
klou
|
|
|
|
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/groups/opt_out.
