On Wed, Jul 12, 2017 at 10:43 PM, William <[email protected]> wrote:
> Proper procedure would be to recognize that work is now available from
the selected project(s), abort all those "Ready To Start" tasks from the
unselected project(s), then calculate how many new tasks are now needed
from the selected project(s) and fetch work from the selected project(s)
accordingly.
If everyone would be requesting a full 7 days worth of work to fill in the
time that the original projects don't have work for one day, then abort
that whole cache of work, none of the work will ever be done. It's also not
how this function works.
You have the option to either have your computer be partially or completely
idle during the time that the original project is in maintenance and cannot
send you work, or for your computer to be busy doing at least some good
work for the other project(s). You chose the last.
If anything should be done, it would be to download enough tasks to fill
the CPUs/GPUs and nothing more, so as not to waste when the original
project comes back. And then download one task every time one task is
finished.
BOINC doesn't recognize tasks though, it works with seconds of work to
download. With a 7 day cache that's a lot of seconds, even for the backup
project.
Also, the option "If there is no work available for the project(s) I have
selected above, please send me work from another project" isn't so much one
of the unselected projects in WCG (although it may be working like that in
this case), but another project you may have added to BOINC (Einstein,
Seti, CPDN, GPUGrid, etc.)
> Requesting that this correct procedure for handling the World Community
Grid's checkbox related to work outages be included within an upcoming
release of the BOINC software.
Yes, that's not going to happen, because it's wasteful and against the idea
behind BOINC (try to finish all work before deadline).
A simpler solution for you would be to add an 8 day cache, so that day that
BOINC downloads work from another project only happens once every 6 weeks,
and even then maybe not.
Or if this is a BOINC 7.6, to set the first value, which is the low water
mark, to 0.5 days and the additional work to 8 days, BOINC will download
enough work to top off the cache every half day. ("Connect to network about
every N days; Cache N extra days of work")
It will then on the day of the outage download enough work from the backup
project to top off the cache. Yes, that work still has to be done, but at
least it isn't a full cache.
-- Jord van der Elst.
_______________________________________________
boinc_dev mailing list
[email protected]
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
