I just added World Community Grit to my Boinc program. It looks like a good one too. My question is...is it possible for the Boinc to run both Rosetta and the World Community Grid at the same time? And if so, how do I do that? It seems that the Boinc will only run one at time now. Is that what the preference option of "Switch between programs...60 min." means? Is it possible to run both at once?

---

The only way you can crunch two projects simultaneously is if you have two CPUs.
Check my profile, look at 'view computers' and you'll see what I mean.

My PC regularly crunches two totally different projects simultaneously!

---

No, If you have only one CPU, it's one project after the other. And yes the" Switch between..." is the key to switch from one app to the other.

Also resource share dictates how much of your CPU time to give to each project over the long term. Example. Project A share 50 and Project B share 100. Project A will have the CPU 1/3 of the time and Project B will have the CPU 2/3 of the time. If possible, it will be 2 hours of B and 1 of A (depending on the switch time). If one of the projects has anticipated deadline trouble, that project will get extra CPU time now, but will not be allowed to download new work for some time in order to let the other project catch up on its CPU time.

---

BOINC WIKI

Also resource share dictates how much of your CPU time to give to each project over the long term. Example. Project A share 50 and Project B share 100. Project A will have the CPU 1/3 of the time and Project B will have the CPU 2/3 of the time. If possible, it will be 2 hours of B and 1 of A (depending on the switch time). If one of the projects has anticipated deadline trouble, that project will get extra CPU time now, but will not be allowed to download new work for some time in order to let the other project catch up on its CPU time.

Thats pretty cool, I didn't know that. I just set one of my rigs onto 3 smaller projects to run for probably a year without me being able to touch them.

---

Also resource share dictates how much of your CPU time to give to each project over the long term. Example. Project A share 50 and Project B share 100. Project A will have the CPU 1/3 of the time and Project B will have the CPU 2/3 of the time. If possible, it will be 2 hours of B and 1 of A (depending on the switch time). If one of the projects has anticipated deadline trouble, that project will get extra CPU time now, but will not be allowed to download new work for some time in order to let the other project catch up on its CPU time.

Thats pretty cool, I didn't know that. I just set one of my rigs onto 3 smaller projects to run for probably a year without me being able to touch them.

Thank you.

I was the developer that did most of the work on the current CPU scheduler.

---

BOINC WIKI

Well phooy. I guess I'll just crunch Rossetta by itself then.

---

Well phooy. I guess I'll just crunch Rossetta by itself then.

Always a choice.

---

BOINC WIKI

Also resource share dictates how much of your CPU time to give to each project over the long term. Example. Project A share 50 and Project B share 100. Project A will have the CPU 1/3 of the time and Project B will have the CPU 2/3 of the time. If possible, it will be 2 hours of B and 1 of A (depending on the switch time). If one of the projects has anticipated deadline trouble, that project will get extra CPU time now, but will not be allowed to download new work for some time in order to let the other project catch up on its CPU time.

Thats pretty cool, I didn't know that. I just set one of my rigs onto 3 smaller projects to run for probably a year without me being able to touch them.

Thank you.

I was the developer that did most of the work on the current CPU scheduler.

Cool. Can you confirm that the 5.5.x versions switch only after a checkpoint and try to finish a WU before switching if it is near completion?

Also resource share dictates how much of your CPU time to give to each project over the long term. Example. Project A share 50 and Project B share 100. Project A will have the CPU 1/3 of the time and Project B will have the CPU 2/3 of the time. If possible, it will be 2 hours of B and 1 of A (depending on the switch time). If one of the projects has anticipated deadline trouble, that project will get extra CPU time now, but will not be allowed to download new work for some time in order to let the other project catch up on its CPU time.

Thats pretty cool, I didn't know that. I just set one of my rigs onto 3 smaller projects to run for probably a year without me being able to touch them.

Thank you.

I was the developer that did most of the work on the current CPU scheduler.

Cool. Can you confirm that the 5.5.x versions switch only after a checkpoint and try to finish a WU before switching if it is near completion?

1) There is no attempt made to wait for a task to finish other than waiting for the next checkpoint. So, if things are running normally, and there is no checkpoint between the re-schedule and the end of the task, it does wait.

2) Tasks normally wait for the first checkpoint after their first allotted time slice since a start from paused. The exception to waiting is if a project requires extra CPU time, in which case it is more important to get started on that task than to wait for a checkpoint that might never come. The second exception is if the task has checkpointed within the last 10 seconds (seconds, not minutes).

Yes, this is in the later 5.5 versions starting, around 5.5.7 I believe. However, please note that 5.5 builds are for Alpha testing, and carry a higher risk of severe problems (for example, the current build will not install on Win 9X).

---

BOINC WIKI

1) There is no attempt made to wait for a task to finish other than waiting for the next checkpoint. So, if things are running normally, and there is no checkpoint between the re-schedule and the end of the task, it does wait.

At Rosetta this leads to WUs stopping at 100% and waiting for the next timeslice for Rosetta. This is not the fault of the scheduler but a consequence of the Rosetta code, that seems at the end to:
- tell Boinc "I'm at 100%"
- write a checkpoint (why?)
- want to clean up and exit, but is replaced by another app before this.
At the next start it loads the checkpoint, cleans up and exits :-)

Norbert

---

Just a quick question.

How does the sceduler cope with WCG. Since (at the moment) WCG is effectively 3 different project (HPF-II, Cancer and HIV) inder the WCG banner. can the current or the 5.5.x series cope with intraproject & interproject scheduling well.

i.e. If I set each of WCG project to 100share (if it has such a thing for it's projects?) and Rosetta to 100% would it do each 4 project equally.
Or would you have to set the overall share at WCG to 300 and hope WCG have figured a server side sharing.

Does the BOINC platform provide for this?

---

Team mauisun.org

WCG is treated as ONE project. The fact there are 3 apps for it makes no difference. Just as other projects with have multiple applications under it's umbrella. Well, that's how I understand it. I have crunched for WCG but they won't show you your "work in progress" via the results page, so you have no way of knowing if/when you'll get credit or even the status of your work. This is the reason they don't have a spot on my "cross project credit parity" spreadsheet. Leiden Classical runs the purger/deleter immediately after validation, so all you can see is "pending" then they're gone. This is why Leiden isn't on my spreadsheet either.

tony

...If I set each of WCG project to 100share (if it has such a thing for it's projects?) and Rosetta to 100% would it do each 4 project equally.
Or would you have to set the overall share at WCG to 300 and hope WCG have figured a server side sharing.

Does the BOINC platform provide for this?

Not clear how they did it, but WCG handles their own subprojects. You simply elect which you'd like to participate in and they schedule those types of WUs to you. I don't believe they allow you to designate resource share within their projects.

So, if you wanted to do all 4 equally, you'd do a BOINC resource share like Rosetta 100, and WCG 300. And then hope that WCG gives you a roughly equal amount of work for each subproject.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

I have crunched for WCG but they won't show you your "work in progress" via the results page, so you have no way of knowing if/when you'll get credit or even the status of your work.

Actually, while it's more difficult to come by, they do show this info for your results, and clicking on a wu shows the status and claims and so on from the other computers also crunching same wu. But, there's no listing of which computer these other results belongs to, so you've no idea if you've been paired-off with a slow p3, or someone running with a 6-day cache...

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."