Drastic queue cleanup

2005-09-10 20:25:22 | johann | #

At the moment, most factories are busy with jobs that have been submitted more than a week ago. Chances are that nobody will ever look at the results. Also, the hard drive on the server is getting very full because of the screenshots that are kept until the last factory for an URL is finished. So I have decided to trim the queue manually and install a queue limit. I'm sorry for those who were really waiting two weeks for their last screenshots to come through.

New jobs will not be accepted for a browser if there are too many jobs queueing for it. This means that if a job is accepted, the waiting time will not be higher than the queue limit. I am not sure where to put the limit, maybe somewhere between 1 and 3 days. If it's too short, many jobs will be rejected during high load times. What do you think?

Good idea

posted 2005-09-11 08:48:01 by beza1e1

After thinking a moment, i concluded this is a good idea. It may piss off a lot of people, if this hits slashdot or similar traffic leaders. On the other hand a slashdot is probably solved some days later and people, who use browsershots for more than fun, can do work again. I'd say: one day

perhaps a way to cancel request

posted 2005-11-17 01:00:44 by dave

I just heard about your service - and added a url just for the hell of it... The queues were so big, my request got cancelled in most of the browsers. So as I didn't really want my shots, and I was just making it worse for everyone, I thought a cancel request button would help.

Right, but we need authentication for that

posted 2005-11-17 09:42:49 by Johann C. Rocholl

We'd have to make people login before they could submit or cancel jobs. Otherwise some people could just cancel other people's requests.