History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-1821
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: Simo Kurra
Votes: 3
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Usability Improvements for the Queue page

Created: 17/Oct/13 12:55 PM   Updated: 15/Nov/13 12:27 AM
Component/s: None
Affects Version/s: 5.0.24
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
The Queue page is "next to useless" in our case. For example currently there are over a 1000 simultaneous builds running. With a hardcoded pagination of 25 navigating to a specific area of the queue is almost impossible - by the time you have figured which page it might be in, the queue has already "lived" enough for it to be something completely different. Each click also takes tens of seconds to load.

While there is probably a good reason that the page is that slow (although any performance improvements would be welcome), a few simple ideas would make the page more usable:
-Possibility to filter items in the queue by the columns that it's possible to sort them by - for example "Only show builds that are of config xxx/yy"
-Possibility to tune the pagination value - 25 is just too low
-grouping builds with hide/expand functionality by parent/child relationship --thus being able to show more per page - when collaped it could just show a number "20 builds currently running in this tree"
-grouping builds with triggered/triggeree relationship - thus being able to show more per page
-Link to node running the build being displayed


 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [15/Nov/13 12:27 AM]
Create a separate ticket for page size adjusting:
http://track.pmease.com/browse/QB-1841

We will make it into QB 5.1, please watch on it.

Simo Kurra [14/Nov/13 09:24 AM]
We upgraded to 5.0.39 and have to say good job on the peformance improvements! The queue page (and UI in overall) is really flying compared to what it was - it's not just a minor improvement, but I'd say several orders of a magnitude improvement.

If performance is not an issue anymore, then would it make sense to increase the amount of builds in the pagination from 25? Or make this option configurable? That would be the simplest from my wishlist to implement and already a big improvement.

The rest are "nice to have", but still, important improvements for our usecases

Simo Kurra [18/Oct/13 08:45 AM]
We have scheduled an update later this month so looking forward to that. And thank you for taking this feedback into consideration :)

Robin Shen [17/Oct/13 11:22 PM]
We will investigate suggestions you provide. As to page loading performance, we removed some more synchronization blocks since 5.0.24. Can you please upgrade to 5.0.38 to see if there are any improvements?