On Monday 06 August 2007 10:13:18 wrote John Pye:
Adrian Schröter wrote:
On Sunday 05 August 2007 14:42:10 wrote John Pye:
Hi all,
In the Build Service Web UI, it seems to me that there is often quite a lag between making changes to one of the files (eg a .spec file) and seeing the correctly updated status for the packages changing to 'building' or 'queued' or whatever.
Often I find myself hitting the 'trigger rebuild' button in this case, but I still don't see any update being shown.
as written before, it is the scheduler you need to wait for.
My concern is that the web interface doesn't even tell the user that they need to wait for the scheduler (or even that such a thing exists).
I understand that you are dealing with the scheduler in some kind of asynchronous way. But there is just nothing about the web interface that tells the user that the request has been received: it's a open-loop user interface.
Yes, I agree, but I think it is not easy to implement this, since the scheduler is actually trying to find out what is affected by the changes. However, it might be possibly to run 1 fast first path, just to mark possible affected projects, which could become a "unclean" tag in the UI ... Adding this as an item to discuss ...
I'd refer you to Jakob Nielson: http://www.useit.com/papers/responsetime.html
The Build Service Web UI is really wonderful overall; I just wanted to emphasis this small issue, because as well as causing usability problems, it could be resulting in quite a bit of additional server load for you.
In General, if "trigger rebuild" does change anything, it is a bug of the build service. The service should always guarantee a clean up and consistent build.
We'll it's true in the sense that it doesn't do anything for 30sec or a minute or so. I consider that too long. I am puzzled as to why theres need to be such a long wait before the scheduler even tells me whether or not something has been scheduled? Surely it's just putting something into a queue?
Just to get you a picture, a new started scheduler does need already 30 minutes to calculate the complete content of the OBS. And even though we will improve the performance of it, I expect it to run longer, since the hosted projects will increase ... -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org