Hallo,

maybe a old question... ?
Boinc 7 don't care about project weight settings... what can i do ?
I run project 1 with 100% and project 2 with 300% ( quad-core ) but only project 2 is running tasks since 3 days now.... project 1 is waiting all the time.
How can i get Boinc to run a project on 3 cores and other project on 1 core continues.

---

Greetz,
Chris

That what you ask isn't project weight, or resource share (which aren't percentages by the way, but just values which when added up are 100%), but processor affinity and that is something BOINC (no matter which version) does not do.

Now it's working as you told it to: Project 2 has the biggest weight, it'll work 3 times more than project 1 will do. And that on all hardware resources (CPUs and GPUs if available and applicable).

---

No, I not agree with this.
With Boinc 6 i give project 1 300% and project 2 100% project weight.
On my quad-core 3 cores work continue at project 1 and 1 core at project 2.

Now all cores work at project 1 ( for 4 days now ) and project 2 units are waiting ( for 4 days now )

---

Greetz,
Chris

BOINC 7 is no longer doing the short term balancing, rather it does it in big blobs, project A, then project B, then back to project A... give it more time and you'll see it will balance. There's one snag in this. It's not time based, rather credit based, so if one project gives 2 times more credit than the other per unit of time, the one with the lower credit is given more time (Think this is how it is... the projects that inflate credit get kind of penalized for doing so, and if true, brilliant... keeps them all honest).

OK... than i know what the problem is...... i also run on of the projects on GPU... so this project makes much more credit....
I think it's time that boinc gets separate adjustments for GPU work... there are more problems with that....

---

Greetz,
Chris

The way I do it: if a project has both GPU and CPU applications, I don't take the CPU workunits and only do the GPU WUs for that project. That leaves more CPU time for the projects that don't have any GPU applications.

To me, a project that doesn't have any GPU apps needs all the CPU time I can give it. But if my GPU is doing work for a project, any additional contribution from my CPU would be relatively minor, because my GPU can work so much faster than my CPU.

So, on my system: Einstein@Home and MilkyWay@Home are only doing GPU applications and getting tons of work done. That leaves more CPU time for Cosmology@Home to plod steadily along (as well as Rosetta@Home, once they get the current bugs worked out).

That seems to work very well for me: no idea if my logic makes sense to anybody else. :)

Edit: just want to add that I started doing this with BOIHC 6.x; it's not something I started in response to the scheduling changes in V7.x.

@tanstaafl9999:

i do it also, but the problem is that WCG and poem doesn't need a GPU core only but need a CPU core also... you can't regulate anything with Boinc there...

---

Greetz,
Chris

Chris,

I just found out about that. A few days ago (after my previous post), I signed up with WCG and quickly discovered that the GPU work units also uses one CPU core.

I'm used to projects where the GPU applications don't take over a full CPU core, which makes allocating resources a lot easier.