Antonis Markouizos wrote:
[...]

Download workunits for 4-5 weeks and let it go.
(dialup? 56k? you should let it download for the whole night, and as many as
it gets. i.e. set it to 500,
and on the morning set it to "finish" one or two "after" those it got down)

_BIG_ QUEUES ARE BAD FOR SETI@HOME!!!


If your queue delays you returning the result for a WU from the TIME OF DOWNLOADING THAT WU for too long, that result is near useless. (And very expensive electricity to just increment your WU count.)

Also, the s@h server must keep a pool of WUs that matches the pool of WUs temporarily lost in everyone's queues, to then later check if enough results have been returned before clearing a particular WU from the pool. Big user queues increase the workload on the s@h database and server.


As to how big a queue is reasonable?...

Various vague comments have been made in the past. There seems to be a concensus that you should have you queue store no more than 1 week's supply of WUs.

My opinion is that you should store no more than two day's supply of WUs to allow for the rare occasion that s@h's servers are offline over a weekend.


The recent reobservations WUs appear to have caused a bit of a glitch in WU distribution... (Users preferentially queuing reobservation WUs into big queues? (;-))


Keep crunchin'
(with a reasonable queue size for your WU crunching rate)
Martin