It may be a straight foreward Answer but i couldent find it in the FAQ.

Is there a limit of computers that you can use for a project?

example;

I have 4 Server computers, all of them have BOINC, and all of them have Rosetta added, yet only one of the computers is actualy working with rosetta, the others are just sitting there, moving dust particles and heating the air arround it.

All 4 Server computers have the same list of projects

Seti
Rosetta
QMC
World Community Grid
Climate Prediction
Protein Folding

I'm looking to add more project in the future

I would like the 4 Server computers to work at the projects at the same time ( one task preformed by 4 computers )

Not meaning that every Server computer is running all added projects it seams to do only 2 at the time

also in the future i'm aiming to add 4 extra Server computers

Am i aiming to high with my current project i have i mind and would it be better to shut down 3 of the servers ?

or am i doing something wrong ?

---

It may be a straight foreward Answer but i couldent find it in the FAQ.

Is there a limit of computers that you can use for a project?

example;

I have 4 Server computers, all of them have BOINC, and all of them have Rosetta added, yet only one of the computers is actualy working with rosetta, the others are just sitting there, moving dust particles and heating the air arround it.

All 4 Server computers have the same list of projects

Seti
Rosetta
QMC
World Community Grid
Climate Prediction
Protein Folding

I'm looking to add more project in the future

I would like the 4 Server computers to work at the projects at the same time ( one task preformed by 4 computers )

Not meaning that every Server computer is running all added projects it seams to do only 2 at the time

also in the future i'm aiming to add 4 extra Server computers

Am i aiming to high with my current project i have i mind and would it be better to shut down 3 of the servers ?

or am i doing something wrong ?

There is no limit as to the number of computers one can have for any project. The more the better as far as I am concerned :)

Each computer will run 1 workunit per CPU. So, if one of your computers has 1 CPU then you can run 1 workunit, 2 CPU--up to 2 workunit's, 4 CPU--up to 4 workunit's, and on. Please note that you cannot work on the same workunit spread over several computers.

The order in which a workunit runs on your computer is determined by the resource share you give to the project that the workunit belongs to. I noticed that you have 6 projects per computer, so if the resource share for all of those projects were equal then each project will have an equal share of time. In short, the greater the resource share for any particular project the greater the amount of time that that project is allowed to run before switching to another workunit.

I hope this helps you out. Please check the Rosetta@home FAQ for more information.

---

Thnx Verry much for your answer

My servers all have Single processors so i guess they wil run 1 project each
it seems now that the other computers will be added sooner then i had anticipated

i kind of hoped that it would be possible to let 4 computers work on the same project

but this is not a real problem i'll keep on crunching

---

To be clear, each computer can be attached to an unlimited number of projects. However, it can run only 1 task per thread (core or HyperThread) at a time. BOINC will alternate between the tasks per the allocation you set.

---

Reno, NV
Team: SETI.USA

you can use every processor on just one project. just click on my username then view computers to see how many I have attached to Rosetta. I'm not sure why the others aren't processing rosetta. It might have to do with your allocated resource shares, or maybe the project is suspended in the manager. I'd need more info to discern that.

the computers that aren't crunching might be 'waiting for memory'. This happens when there isn't enough memory available for the task to run.

The amount of memory available is determined by your project preferences (under the participants menu above) - there's an amount of memory BOINC can use while the computer's in use, and an amount BOINC can use when the computer is idle. If the task requires more than is available, it will stop processing. It should try and start another task that requires less memory in the mean time, but this doesn't always happen at the moment.

If this is the cause of your idle computers, you could try increasing the amount of memory available to Rosetta on your preferences page.

Other reasons they might not be crunching are: not enough disk space remaining, too much disc space used, etc etc - have a look under the messages tab in BOINC Manager for the reason given.

HTH
Danny

---

I thank you all for your reply as you may have noticed its been a while since i last reply'd

i now use 1 single Quad Core CPU for 6 projects but aim to change that in the future by adding more computers to do the crunching of thet date send bye the projects

my goal is to have 10 Quads working at 10 projects each Quad having 1 Project to work on

now i wish to ask

is there another way to increase the crunching of projects faster then normal ?

like overclocking the CPU of other ways?


my Quad core that i use now for the 6 projects has been overclocked from 2.4 Ghz to 3.1 Ghz and the FSB went from 1066 to 1333 mhz

would that increase the rate of processing =

thnx again

---

is there another way to increase the crunching of projects faster then normal ?

like overclocking the CPU of other ways?


my Quad core that i use now for the 6 projects has been overclocked from 2.4 Ghz to 3.1 Ghz and the FSB went from 1066 to 1333 mhz

would that increase the rate of processing =

thnx again

Overclocking does increase the rate of processing. I don't believe the FSB makes much difference to Rosetta on modern computers, but the clock speed does. The other thing you can do is reduce the amount of other processing the machine does - i.e. shut down any unused services such as the print spooler service etc if you're using Windows.

Danny

---

Overclocking does increase the rate of processing. I don't believe the FSB makes much difference to Rosetta on modern computers, but the clock speed does.

I think it depends. I have a 8-core Mac Pro based on Penryn Xeons, and overclocking seemed to have made a bigger difference than it should have, so I suspect that the faster FSB probably removed a bottleneck (8 cores all working at 100% might be maxing out the FSB, so overclocking it helps).

Probably not an issue with just 2 cores, though.

---

I thank you all for your reply as you may have noticed its been a while since i last reply'd

my goal is to have 10 Quads working at 10 projects each Quad having 1 Project to work on

now i wish to ask

is there another way to increase the crunching of projects faster then normal ?

like overclocking the CPU of other ways?


my Quad core that i use now for the 6 projects has been overclocked from 2.4 Ghz to 3.1 Ghz and the FSB went from 1066 to 1333 mhz

would that increase the rate of processing =

thnx again

I've found that some projects do not have workunits available; for example, Rosetta@home, boincsimap, and Cels@Home. If you devote a computer to any of these, the computer will not always have something to work on, so you need a backup project for those computers to work on.

I've found another way to increase the speed that should work on some computers - replace the memory with faster memory. It worked on mine. I also got more memory at the same time, up to the maximun my machine allows, since I noticed some non-BOINC work slowing down too much and decided I did not have enough memory to run both the BOINC projects and the non-BOINC work at full speed at the same time. However, note that most 32-bit operating systems have a hard limit of 4 GB on how much memory they are able to use.

Allowing BOINC projects to use 100% of the idle time also helped.

Selecting the leave-in-memory option eliminated some of the time needed to restart workunits after working on a workunit from another project for a while.

Yes, so actually you'd be better off to take 10 systems, and perhaps divide them into two groups. One group is set up for 20% resource share for each of 5 projects, and the other group is set up for the other 5 projects. Assuming you want an equal resource share. The idea being to reduce the number of projects per machine. But not clear down to just any 1 project on a machine.

---

Rosetta Moderator: Mod.Sense

Damn. We have some strong CPUs in this project :D

I'm glad we have some strong dedicated users in Rosetta@Home.

Now let's just hope for a GPU Rosetta@Home ;)

---

Yes, so actually you'd be better off to take 10 systems, and perhaps divide them into two groups. One group is set up for 20% resource share for each of 5 projects, and the other group is set up for the other 5 projects. Assuming you want an equal resource share. The idea being to reduce the number of projects per machine. But not clear down to just any 1 project on a machine.

All of my machines have rosetta@home alone. And haven't had any problems... except when Rosetta has some WU problems... thats why I increased the work cache to 3 days.

---