I don't know if anyone at BOINC will read this but I have two suggestions for improvements of the BOINC program that will hopefully make the system more efficient and easier to manage:

1. Many people have the BOINC Cleint program running on multiple computers. Currently, anytime a new project comes out users have to go to each and every computer they are using to attach to the new project, one-by-one, client-by-client. This can be time consuming, especially for users who have many computers such as universities.

Rather than having users attach to new projects one-by-one, client-by-client, BOINC should make attaching to a project as easy as visiting an accounts on the BOINC website. In other words, I should be able to log-on to BOINC's website and attach to the new project online. The next time my Client programs on my all my computers connect to the BOINC server they will receive a message to attach to the new project.

2. Not all computers are effecient at processing certain projects. For example, I have two super-fast computers, each with dual processors that crunch through the more complicated projects like climateprediction.net work units better than my laptop. The BOINC website should be able to analyse the general efficiency of all my computers to process the various projects I am attached to holistically and assign each computer's work share according to the computer's ability to process work units.

For example, my slower computers can't process climatepredition.net work units very quickly but they can process SIMAP with relatively good efficiency so BOINC should assign the heavier work loads like climateprediction.net to the faster computers on my account.

---

I don't know if anyone at BOINC will read this but I have two suggestions for improvements of the BOINC program that will hopefully make the system more efficient and easier to manage:

1. Many people have the BOINC Cleint program running on multiple computers. Currently, anytime a new project comes out users have to go to each and every computer they are using to attach to the new project, one-by-one, client-by-client. This can be time consuming, especially for users who have many computers such as universities.

Rather than having users attach to new projects one-by-one, client-by-client, BOINC should make attaching to a project as easy as visiting an accounts on the BOINC website. In other words, I should be able to log-on to BOINC's website and attach to the new project online. The next time my Client programs on my all my computers connect to the BOINC server they will receive a message to attach to the new project.

2. Not all computers are effecient at processing certain projects. For example, I have two super-fast computers, each with dual processors that crunch through the more complicated projects like climateprediction.net work units better than my laptop. The BOINC website should be able to analyse the general efficiency of all my computers to process the various projects I am attached to holistically and assign each computer's work share according to the computer's ability to process work units.

For example, my slower computers can't process climatepredition.net work units very quickly but they can process SIMAP with relatively good efficiency so BOINC should assign the heavier work loads like climateprediction.net to the faster computers on my account.

I belive that there is something like #1 in testing at the moment.

You may want to sign up for the developers and the alpha newsletters. Can't remember where I signed up, but probably somewhere on the main BOINC page. I only read to learn about new things and most of the stuff is so far above my head... well... I'm a computer dummy :)

Kathryn

---

Kathryn :o)

Number 1 is already been tested when its ready all will know

edit: Doesn't BOINCview already do that for windows machines anyway, you can always use that until the AMS is ready

Number 2 is a hell of alot harder and time consuming for developers, it works good enough as it is now.

If you have slower computers simple, don't sign them upto CPDN

---

Join us in Chat (see the forum) Click the Sig

Number 2 is a hell of alot harder and time consuming for developers, it works good enough as it is now.

If you have slower computers simple, don't sign them upto CPDN

What if an option to limit the number of CPUs a project uses existed on a per-project basis, overriding the same global setting?

Or perhaps adding an option limiting the number of instances of a project that are run at the same time. So instead of requesting WUs good for (time * #CPUs), it would request only (time * #CPUs Limit).

For instance, I run several projects on all my systems, but on the MP ones I'd be glad to run just one instance of a heavy-weight project like CPDN while running one or more instances of other projects.

Right now, the global setting limiting the number of CPUs to use applies to the BOINC client, not each project.

---