Allegedly, Boinc has the capability to run multiple projects simultaneously. I attached to Climate Prediction (alone) and Boinc ran just fine. Then I attached to Seti@home in Boinc. Seti@home attached just fine. The projects tab show that both programs were connected and using 50% of the resources each.
However, the Messages tab showed that Climate Prediction was paused and removed from memory. At this point, nothing would restart (unpause) Climate Prediction in Boinc. I tried stopping, starting, uninstalling, and reinstalling Boinc. Meanwhile, Seti@home continued to compute without any problems.
Nothing restarted Climate Prediction, until I disconnected from Seti@home. After I stopped and restarted Boinc, Climate Prediction ran just fine, again. Apparently, Boinc cannot really share Seti@home and Climate Prediction on a single processor.

---

Hi GM

It depends on your definition of "share".

BOINC's definition, is that it runs project 1 for X hours, and then swaps over and runs project 2 for Y hours.
Values for X and Y are defined in your preferences. (Your account, to the left of here).

Les

BOINC has a concept of resource debt. When you connect to a new project it will be assigned a period of time that it needs to run continuously to make up for the time your other projects have already run. The same thing will happen whenever you change the relative resource shares.

Personally I don't believe that resource shares should be applied retrospectively. But I only run CPDN, so such issues don't affect me :)

It should be possible to prevent BOINC from running a new project to the exclusion of the others by stopping the program and editing the <b>client_state.xml</b> file in your BOINC directory. Search for the tag <b>debt</b> and change the value to <b>0.000000</b> everywhere it's found.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

If you read the BOINC documents, BOINC would rather get 1 Project (P) done in 1 Time Unit (T) than 2P in 2T. Logically: One unit will be ready first sooner, and the second will be ready afterwards, instead of both won't be ready until the end.

E.gs:
Hours: 0-----1-----2
MethA: 0-----A-----B
MethB: 0-----------A+B

You get results sooner the way BOINC does it now, than having 10 running "all at once".

---

&gt; If you read the BOINC documents, BOINC would rather get 1 Project (P) done in
&gt; 1 Time Unit (T) than 2P in 2T. Logically: One unit will be ready first
&gt; sooner, and the second will be ready afterwards, instead of both won't be
&gt; ready until the end.
&gt;
&gt; E.gs:
&gt; Hours: 0-----1-----2
&gt; MethA: 0-----A-----B
&gt; MethB: 0-------------A+B
&gt;
&gt; You get results sooner the way BOINC does it now, than having 10 running "all
&gt; at once".
&gt;
Not to mention that it will take longer to run 2 at the same time due to the added overhead. I edited the graph appropriately.

---

BOINC WIKI

BOINCing since 2002/12/8