[RC5] Request: Fetch by Units of Work
Basil A. Daoust
basildaoust at home.com
Sat Jan 8 04:04:32 EST 2000
One solution is to set the packet size to 28 if you need less than 500
work units. This will ensure you get at least what you requested.
Alternately why not just request say three times as many packets
as you think you will process in x hours. That way if
your tied up, the machine will happy continue on. And you did
say rc5 so no need to worry to much of stealing packets someone
Just my 2 cents
Mikus Grinbergs wrote:
> My system runs offline. Any particular attempt to establish a
> connection to the net may have problems, and may have to be
> done over. As a result, I make all my connections manually.
> I would like to "schedule" my time - i.e., When is the next time
> that I need a net connection? (I know from experience how many
> hours it will take to process a given number of units of work.)
> But the RC5 software only lets me specify the number of 'packets'
> to fetch, and I have no advance knowledge of how many work units
> that number of packets will bring. So my initial fetch request
> is sized for a planned duration of time - on the assumption that
> I will get mostly "large" packets. Whenever the amount of work
> actually brought by this request is less, I have to re-estimate
> the packet threshold to make up the difference, and then perform
> a second fetch.
> It would help my situation if distributed.net would let me specify
> the quantity I want as the number of Units of Work, rather than as
> the number of Packets.
> To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
> rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5