Ok, my work units are piling up. Presumably this is because of:

Weekly Outage and Initial Catch Up
Every Tuesday morning (Pacific time) we begin a 3 day data distribution outage to focus on science processing and development plus any needed systems maintenance. The upload/download servers will be offline during this time. The web site (including the forums) will only be offline during the database maintenance and backup portion of the outage. On Friday, you may experience connectivity issues as the servers catch up with demand.

I would like to be able to set up a backup project to run when I can't get any SETI work to do. Note: This is not the same thing as just adding a second project. That just splits the CPU between the two, which I don't want if SETI has work to do.

So:

If SETI has work to do, it gets 100% of the CPU, regardless if project 2 also has work to do.

If SETI does not have work, project 2 gets 100% until SETI gets work to do, then it shifts 100% back to SETI (and preferably just pausing immediately project 2 rather than finishing up project 2's current WUs.)

---

Ok, my work units are piling up. Presumably this is because of:

Weekly Outage and Initial Catch Up
Every Tuesday morning (Pacific time) we begin a 3 day data distribution outage to focus on science processing and development plus any needed systems maintenance. The upload/download servers will be offline during this time. The web site (including the forums) will only be offline during the database maintenance and backup portion of the outage. On Friday, you may experience connectivity issues as the servers catch up with demand.

I would like to be able to set up a backup project to run when I can't get any SETI work to do. Note: This is not the same thing as just adding a second project. That just splits the CPU between the two, which I don't want if SETI has work to do.

So:

If SETI has work to do, it gets 100% of the CPU, regardless if project 2 also has work to do.

If SETI does not have work, project 2 gets 100% until SETI gets work to do, then it shifts 100% back to SETI (and preferably just pausing immediately project 2 rather than finishing up project 2's current WUs.)

Upgrade your BOINC install to 6.10 and set the resource share for the backup project ot 0.

---

BOINC WIKI

The current version allows for a back up project - resource share of 0. This only works with projects that have updated their Boinc server software. It also tends to fill the cache per your settings. This feature is still under development so it doesn't work as you would like. The next release version should only get enough work as needed to keep the CPU busy until your main project is available.

The current version allows for a back up project - resource share of 0. This only works with projects that have updated their Boinc server software. It also tends to fill the cache per your settings. This feature is still under development so it doesn't work as you would like. The next release version should only get enough work as needed to keep the CPU busy until your main project is available.

I still think that even the backup project needs to fill the queue to "Connect every X" so that dialup users can maintain enough work on hand.

---

BOINC WIKI

I think someone (possibly JM7) wrote that connect cache should be filled and addition cache ignored for back up projects. Memory fails...

I think someone (possibly JM7) wrote that connect cache should be filled and addition cache ignored for back up projects. Memory fails...

Yes, me. I don't think it works that way at the moment. I believe it takes a completely dry CPU to get work from a backup project (with 6.11 code anyway).

---

BOINC WIKI