Re: work unit rotation
Mike Reed <[email protected]> Wed, 5 Sep 2012 19:46:32 +0100
| Newsgroups | gmane.comp.distributed-net.rc5 |
|---|---|
| Message-ID | <CACwkm_PmSoDbUaHe5xbE3gVjX2h8tkkG16iPrd4NovwhkE7Abw@mail.gmail.com> |
Hi, The logic we use selects the oldest first. Don't worry about the rotation; spaces get re-issued eventually. The space for rc5-72 is very big, so we'll be doing this for a while yet. Kind regards, Mike On Sep 5, 2012 4:38 PM, "jp68" <[email protected]> wrote: > I have a couple systems that I sneaker net using a usb scandisk to > exchange the work units. And the new work units to a system are added > to the buff-in file using the -import function. In the past I have > added different sized work units to the buffer file, and have noticed > that the dnetc client first chooses any partially crunched units and > completes those before starting on wholly uncrunched units. I've also > noticed that if different sized work units are added to the buff-in > file, that the dnetc client will start crunching the smaller units (like > a 16 stats unit work unit before a 32 stats unit work unit) and work up > to completing the largest stats unit work units last. What I'm > wondering is if there is any work unit date/age selection involved so > that the oldest work units in the buff-in file would be completed before > newer ones were?? > > _______________________________________________ > rc5 mailing list > rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected] > http://lists.distributed.net/mailman/listinfo/rc5 > _______________________________________________ rc5 mailing list rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected] http://lists.distributed.net/mailman/listinfo/rc5