|
||||||||
|
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.
The queue handling time depends on extensions you use: TaskQueueDispathers, JobProperties, Nodes, ...
As example, there was a severe performance issue in Throttle Concurrent Builds Plugin several months ago.
Operations like canTake() lock the queue and may take much time, hence the issue is valid.
BTW, the only way to fix it inside the core is to implement support of multiple queues within the core (there was a feature request for this case). It would be useful to features like priorities, but the implementation in the current core seems to be extremely hard
@Martin
If the issue is actual to you, please provide a list of plugins you use.