simple question.

Switch from main project to secundaire when Main-project is down.

I do rosetta@home, but when i get a no work message is could take 3 min or sometimes 1 day like 2 days ago for new work.

Is it possible too let 1 project be a main project (rosetta) and when it's down, boinc will start the secundairy project (uFluids in my case) until then.


Now i have rosetta and uFluids.
I now have aFluids shutdown manually because rosetta is my main project.

rosetta has 300 point uFluids 100 (75%/25%)
This from the manager.

---

You could have a main project with a ressource share of say 1000 and a backup with a ressource share of 1. That way the backup project would only get 1/1000 of your total CPU contribution.

---

i have come up with a work around, you can run 2 (or more projects) and place your main project on a high "Resource share" number like 400-500.
now you put your other projects on 1.
400-1 will give 99,75%/0,25% division.

now when a project in the case of 2 is down, out of work, the other will get 100% of the idle cpu time.


i don't find this ideal because you now have take up more resources when you use 2 projects.
With uFluids it's 7MB, can be much more for other projects.


PS:EDIT:didn't see andre's reply, but that's about what i did

---

i have come up with a work around, you can run 2 (or more projects) and place your main project on a high "Resource share" number like 400-500.
now you put your other projects on 1.
400-1 will give 99,75%/0,25% division.

now when a project in the case of 2 is down, out of work, the other will get 100% of the idle cpu time.


i don't find this ideal because you now have take up more resources when you use 2 projects.
With uFluids it's 7MB, can be much more for other projects.


PS:EDIT:didn't see andre's reply, but that's about what i did

When the 2nd project starts a WU this WU do have a dead-time
I believe that with this setup u will *not* meet deadlines
of the secondary project (resource share 1)
U waste u CPU time crunching that WUs that does not meet deadline

Thus, IF no work, better powering off the pc to save electrical power
Maye be , a week later, try again IF now there is work ...

Else, crunch 2 projects with a share 100 for each 50% for each one
and pray that does not occurs of both projects w/o WUs at same time

---

Click signature for team stats

All the details about running a Backup Project are available in the wiki.

---

BOINC WIKI

BOINCing since 2002/12/8

When the 2nd project starts a WU this WU do have a dead-time
I believe that with this setup u will *not* meet deadlines
of the secondary project (resource share 1)
U waste u CPU time crunching that WUs that does not meet deadline.

Carlos,

No, a resource share of 1 will not waste the WU or CPU time. As the deadline nears for the secondary project WU, BOINC will temporarily go into Earliest Deadline First mode, ensuring that even the smallest share meets it's deadline. Just thought I'd clear that up for all.

Michael

---

"The arc of history is long, but it bends toward Justice"

To make this work, you need a secondary project that has both small and quick WU's and has a long dead line. If you use one that takes a long time, then you will keep getting into EDF mode and have to spend a lot of time on the secondary project.

What BOINC needs is secondary project(s) support. No work would be downloaded for a secondary project unless the Primary projects are all out of work. And then it would only download one WU (or a number you set) at a time and when it is done, check the Primary projects for work before requesting additional secondary work.

What BOINC needs is secondary project(s) support. No work would be downloaded for a secondary project unless the Primary projects are all out of work. And then it would only download one WU (or a number you set) at a time and when it is done, check the Primary projects for work before requesting additional secondary work.

You might be interested in trux's Calibrated BOINC Core Client, available at http://boinc.truxoft.com/core-cal.htm. While it was developed to increase the accuracy of credit claimed under SETI when using optimized science applications, the "priority_projects" option that's included might be just what you're looking for.