I use Q9450 + ATI HD4870.
What project shares optimal settings to force BOINC to run 4 SETI and ~3 MW tasks simultaneously?
For now it either starts too many MW tasks and leaves one CPU core idle (only 3 SETI tasks running) or runs 4 SETI tasks and no MW tasks in parallel at all...

What BOINC version are you using?

---

Calm Chaos Forum...Join Calm Chaos Now

6.6.36

I think you'll find that most MW ATI crunchers don't like that version due to its scheduler quirks, but maybe it will work for you. I'm using 6.6.20.

I have the MW resource share well above any other project, that should allow it to consistently run MW and run other projects too. I'm running three projects, MW 400, Spinhenge 100, and Aqua 100.

The running of too many MW tasks is an ongoing issue, you can limit it (somewhat) by adjusting the "cmdline" parameters in the app_info file. I'm not using any of the parameters on my Q9450s w/ 512MB 4850s, but on my i7 with a 1GB 4850, I use "n4 w0.7" in the cmdline. It still occasionally "says" it is running more than four, but not that often. When this happens I suspend all MW WUs that haven't started and the ones that "say" they are running, and let the ones that are actually running finish and upload, then restart the suspended WUs. The MW goes back to running 1, 2, 3, or 4 WUs and the rest are waiting to run or ready to start. And some days it just seems to work better than others. Yesterday was a bad day, today has been a good day.

Hope that's at least a place for you to start, others may have different ideas on how MW should be set up, but this works for me.

---

Calm Chaos Forum...Join Calm Chaos Now

Thanks for description, I setted 6/7 to MW and 1/7 to SETI.
Ultimately I want tune to such state when both CPU and GPU are busy and no babysitting required.
Currently, despite of high resource share, BOINC runs 5 SETI tasks and no MW tasks - GPU stays idle...
I used 6.6.20 before too, but due to some another issues required to install 6.6.36.

I have my Quad set to run SETI at 850 and MW at 150. Occasionally it might start more than 10 MW but not all that often.

---

Having 3 SETI and MW running is a good idea - if my CPUs are jam packed with another project, it can increase MW times by a noticeable %.

If you still want 4 SETI + MW, then goto app_info.xml in your MilkyWay folder, and change this:

    <avg_ncpus>0.01</avg_ncpus>

0.01 means no. of CPU per WU. So if you get 24, BOINC will assume that MW is using 0.24 CPU. As this is less than 0.5, it'll open up all the cores for SETI.

But I reiterate, I've seen times for WUs on milkyway to increase if all my cores are busy. In terms of a noticeable amount of thousands of credits per day per 4850.

---

Thanks, will try it!
SETI is the first priority project here so will go with 4+24 mode.
Currently my MW RAC still increasing, will see where it will stabilize...