On our servers we just removed the queue completely and replaced it with a link to a separate page that shows the queue. So it gave us one less ajax request per user as well. But we made those changes in core since it was before the queue became a widget.
Before we upgrade to the next LTS my plan is to make that into an official plugin, unless someone beats me to it since it will take some time for us to get there. Robert Sandell Software Tools Engineer - SW Environment and Product Configuration Sony Mobile Communications From: [email protected] [mailto:[email protected]] On Behalf Of Vincent Latombe Sent: den 26 november 2013 18:38 To: Jenkins Dev Subject: Re: Display of large build queue puts heavy strain on browser PR#1014 [1] is answering partially to this problem by making the build queue collapsible [1] https://github.com/jenkinsci/jenkins/pull/1014 Vincent 2013/11/26 Thobias Karlsson <[email protected]<mailto:[email protected]>> Hi, Has anyone found a nice solution to this issue yet? Br, Thobias On Saturday, May 25, 2013 1:20:26 AM UTC+2, Michael Tautschnig wrote: Hello Jesse, On Thursday, 23 May 2013 15:11:54 UTC+1, Jesse Glick wrote: [...] I guess you mean that there ~10k items (such as jobs) in the queue? That will certainly outscale the current build queue UI; it is designed to handle only a few items. Ok :-( Options: 1. Patch the standard build queue widget to only show the bottom, say, twenty queue items, and just display a note that 9980 other items are in the queue. Probably we need to do the same for the node/executor list: display only a limited number of nodes, and only a limited number of executors per node. There can be another page somewhere (RootAction) which displays all queue items, nodes, and executors in a paginated UI (say 100 per page), maybe with filtering etc. Where in the code is the build queue (display) implemented? I'm not worried about executors at present, as there is a relatively small number of them only (yes, full builds do take several days, but that is ok). 2. Write a plugin offering an alternative BuildQueueWidget which behaves as described in #1, for use in big installations. These are now (1.514+) supposed to be pluggable. Right, I figured those changes out from the code. But thus far I'm a user of Jenkins only, so I'll probably wait for someone to come up with such a plug-in. Would be really nice, though. Best, Michael -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:jenkinsci-dev%[email protected]>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
