I've two systems with ATI GPUs that i use for MilkyWay as Seti doesn't have a ATI app. In some way it is working ok, but the overall behavior is very strange.

If i give MW a little to much priority (either through resource share or through ncpu-settings in app_info) it will suspend some Seti-tasks (up to 4cores on i7 HT with 8 cores) the only setting i've yet found to prevent MW from that is to set ncpus to a very low value, actually 0.01. This is because MW starts every task i download imideately, i've sometimes more than 50 MW tasks loaded while there are only 2 tasks really crunshed, the others "only" stay in memory, which makes up to 1GB RAM dedicated to MW.

Is there any setting with that i can define/limit the number of tasks a project can run.

Is it possible to set up two independant BOINC installations one for CPU and one for GPU? That would solve all my BOINC problems and i think that would do the trick for all CPU/GPU problems - that are completely different systems and should be handled differently. I would love to see different BOINC-datafolders for each type of processor. think about other types of xPUs, someone mentioned soundcards or simply two different GPUs ATI/NVidia. They will never get that sheduled correctly.

I asked that some time ago over at MW but couldn't find a solution and i think here are more experienced people around especially with running different projects on CPU and GPU

Sounds odd, have a look at implementing MW ATI optomised app from zslip.com. It may help. I run optimised seti and WM but don't use ATI as I run CUDA cards.

Rob.

---

Thanks Rob, forget to tell that i already use optimized apps from zslip. I don't think there are any stock ATI apps, but not sure.

Oh, some other data:
Core i7 HT enabled (8cores) running Vista Business 64 bit and it's a ATI 4850 with latest drivers 9.4. Seti is running with sse3 optimized AP apps only.

The total output from these systems is impressive ~12k Seti and ~40-50k MW depending on work availability

BTW it looks like this in task-manager:

There are no stock ATI apps at MW.

I have this problem occasionally, and it seems to be related to the number of CPU tasks you have sitting in your queue. If it gets too low, the GPU apps start going crazy.

When I happen to see this on my PCs, I suspended all of the MW tasks that say they are running but really aren't, and let them go one at a time for a couple then you should be able to resume the rest of the MW WUs and it will work normally (for a while anyway).

---

Calm Chaos Forum...Join Calm Chaos Now

That's why the problem became urgent again. Seti filled my cache completeley so that MW didn't even try to download new work. That's why i set Seti to get no new work and after some time MW went crazy. Now i have the problem if i let Seti do, it will prevent MW from working and if i limit Seti MW will get crazy.

To let them run one by one isn't really an option, as it actually gets a lot of work and the 4850 does it in seconds so i have to babysit it all the time.

How large is your cache set? MW doesn't really like caches larger than the 3 day deadline.

If you have it larger than that, you might try lowering it to 1.5 or 2 days. I run a 1 day cache and is always requesting work.

---

Calm Chaos Forum...Join Calm Chaos Now

Cache could be the "problem", i'll try that when my seti work will be 2 days or less. At the moment i've seen another behavior that helps staying busy at MW as it seems that boinc is always requesting work when it's "crazy". When it's normal it only asks when the current work is done