World Community Grid "Waiting to Run" What gives? I have SETI@HOME running fine but I also want to run "World Community Grid" as well. The problem is that at the Status screen I have "Waiting to run" I can't get it to start. Is SETI eating up all the resources and letting other projects work?

I'm using Boinc to run everything.

---

Machine A.
Ubuntu 7.04 (Linux)
Intel Pentium 4 HT @ 2.8Ghz FSB 800
1024 DDR2
Nvidia GeForce 6200 TurboCache, 256 GDDR2

Machine B.
Windows XP SP2
AMD64 @ 1.8Ghz FSB 800 (Socket754)
1024 DDR 400
ATI Radeon X800 Pro, 256 GDDR3

World Community Grid "Waiting to Run" What gives? I have SETI@HOME running fine but I also want to run "World Community Grid" as well. The problem is that at the Status screen I have "Waiting to run" I can't get it to start. Is SETI eating up all the resources and letting other projects work?

I'm using Boinc to run everything.

Now is the other way around... Now SETI@HOME "waiting to run"


Is this happening because BOINC can only run one task at a time? I just want to be able to run several task at the same time.

---

Machine A.
Ubuntu 7.04 (Linux)
Intel Pentium 4 HT @ 2.8Ghz FSB 800
1024 DDR2
Nvidia GeForce 6200 TurboCache, 256 GDDR2

Machine B.
Windows XP SP2
AMD64 @ 1.8Ghz FSB 800 (Socket754)
1024 DDR 400
ATI Radeon X800 Pro, 256 GDDR3

One project per processor. So single processor machines can only run one, as running more than one would slow things down more than half. It'd be about 1/3 the speed than having it one per processor.

If doing more than one project on multi-processor machines, BOINC works on a debt system, so it will not always be one of each running, but could be 2 of the same. Trying to force it to otherwise will cause issues.

Let BOINC do it's job. It runs well on it's own, without interference.

---

My movie https://vimeo.com/manage/videos/502242

One project per processor. So single processor machines can only run one, as running more than one would slow things down more than half. It'd be about 1/3 the speed than having it one per processor.

If doing more than one project on multi-processor machines, BOINC works on a debt system, so it will not always be one of each running, but could be 2 of the same. Trying to force it to otherwise will cause issues.

Let BOINC do it's job. It runs well on it's own, without interference.

Thank you for your reply. Would you please tell me more abut this Debt system. What is it and how does it work?

---

Machine A.
Ubuntu 7.04 (Linux)
Intel Pentium 4 HT @ 2.8Ghz FSB 800
1024 DDR2
Nvidia GeForce 6200 TurboCache, 256 GDDR2

Machine B.
Windows XP SP2
AMD64 @ 1.8Ghz FSB 800 (Socket754)
1024 DDR 400
ATI Radeon X800 Pro, 256 GDDR3

Basicaly, the project(s) that have tasks running will decrease their debt (yes, I know that it seems backwards, I inherited the direction). Projects that do not have tasks running will have their debts increase. This is in general, there are some special cases on multi CPU systems where the first statement may not be strictly true.

There are two debts tracked - Short Term Debts are tracked for those projects that have work that is downloading, or downloaded but not completed on the host. Long Term Debts are tracked for all projects. Both are (currently) set so that the average is 0. Short Term Debts for projects that do not have work on the host are set to 0. The preference for the CPU scheduler when picking a project to run is to pick the project with the highest STD, but the CPU scheduler will override this to ensure that deadlines are met (Earliest Deadline First). Work Fetch attempts to fetch work from the project with the highest value for LTD - work on hand that is contactable. There are a couple of exceptions here also - most notably because the servers ignore the deadlines of tasks already on the client, a project will not be asked for work if it is in deadline trouble.

---

BOINC WIKI

Thank you for taking the time to explain this to me. I'm doing lots of reading, I like the idea of donating CPU time best way possible.

---

Machine A.
Ubuntu 7.04 (Linux)
Intel Pentium 4 HT @ 2.8Ghz FSB 800
1024 DDR2
Nvidia GeForce 6200 TurboCache, 256 GDDR2

Machine B.
Windows XP SP2
AMD64 @ 1.8Ghz FSB 800 (Socket754)
1024 DDR 400
ATI Radeon X800 Pro, 256 GDDR3