BTW, I confirm that the current implementation may cause huge calculation efforts in the case of big number of jobs with a same category:

  • keySet() causes a useless copy of the data
  • copy to a new array leads to an additional copy of items

It makes sense to extend a the cache's lock time, but to iterate the HashMap directly.

I'll reassign issue to Jesse Glick, who is an author of https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/10
Jesse, do you have some time to fix the issue? If no, I can do it on my own

Change By: Oleg Nenashev (17/Dec/13 5:39 PM)
Assignee: Oleg Nenashev Jesse Glick
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.

Reply via email to