I utilise the backup project function on all my computers. On my old P4 I run SETI (cpu) and MW (gpu) as the main projects with DNETC and Collatz as backup projects. With the recent changes at SETI with regards to beginning a "3 day data distribution outage" I increased the cache on that machine from 0.5 days to 2 days. The backup project function came into use when MW ran out of work so BOINC downloaded work from DNETC.

Well done BOINC this part worked a treat. However, the amount of work downloaded was 2 days worth! Since the project outages typically last less time than this (well not any more with SETI - but that can be managed), it's not really what I'd like to see as BOINC to do. I'd prefer it only download enough work for an hour - which is the length of time the initial backoff occurs when project is down for maintenance.

---

Paul.

Yeah, I flagged that one as well, but have so far been ignored. The funny side-effect is that when your other projects have work again, all the work for DNETC will be ignored until it's about to run out of deadline... and then it will either run in high priority, or kill the work with deadline troubles. Sigh.

---

Yeah, I flagged that one as well, but have so far been ignored. The funny side-effect is that when your other projects have work again, all the work for DNETC will be ignored until it's about to run out of deadline... and then it will either run in high priority, or kill the work with deadline troubles. Sigh.

I've not seen that behaviour since the backup so far has been for gpu projects which BOINC processes on a FIFO basis, but I may see it with the long SETI outrage now in progress.