any idea why the file dnetc518-win32-x86-stream.exe is using 90%+ of the cpu? I don't seem to remember any file doing that in the past. I'm not crunching any WU's on the processor, just the GPU.

FYI - I'm trying to get a second 5870 to run (no success yet). The second card was installed when the file was running around 100% of the cpu, when I removed the second care the file use of the cpu went back down to 0 - 2%.

There is a long standing bug in OpenCL applications that affects dual GPUs (either on one card or two single GPU cards). The bug grabs a complete CPU Core for each GPU running. There is nothing the Project can do about it - has to be fixed at the OpenCL/AMD/NVidia side of life.

Its slowly getting resolved, its been around for a few months now - only affects those with more than one GPU running on a box. AMD recently started testing a Linux fix, its not yet known when the Windows fix will be out. Spring next year would be a crude guess - its a nasty one to resolve apparently.

Regards
Zy

There is a long standing bug in OpenCL applications that affects dual GPUs (either on one card or two single GPU cards). The bug grabs a complete CPU Core for each GPU running. There is nothing the Project can do about it - has to be fixed at the OpenCL/AMD/NVidia side of life.

Its slowly getting resolved, its been around for a few months now - only affects those with more than one GPU running on a box. AMD recently started testing a Linux fix, its not yet known when the Windows fix will be out. Spring next year would be a crude guess - its a nasty one to resolve apparently.

Regards
Zy

Thanks for sharing the information, I'd really not like to have my 4 year old processor crunching 100%, it already has 1 1/2 years of 100% crunching when I first got it.

I guess I'm just going to run one of them for Moo than, and one for another project, unless it's an issue regardless if the cards are split between projects.

There is a long standing bug in OpenCL applications that affects dual GPUs (either on one card or two single GPU cards). The bug grabs a complete CPU Core for each GPU running. There is nothing the Project can do about it - has to be fixed at the OpenCL/AMD/NVidia side of life.

Its slowly getting resolved, its been around for a few months now - only affects those with more than one GPU running on a box. AMD recently started testing a Linux fix, its not yet known when the Windows fix will be out. Spring next year would be a crude guess - its a nasty one to resolve apparently.

Regards
Zy

You must work longer hours then!!

Dont be concerned re the 100%, its built for it, uses a bit more power, not much more, but some - otherwise no cause for concern. Its never a good idea to o/c a CPU to the hilt and run at 100% 7x24, but other than that extreme case, just let it run.

Splitting cards between Projects is practical, but often a drame/nightmare to get right. Much better to leave it where it is. Even not crunching a CPU WU on that core is fine, they always reduce the GPU output - and you lose far more by running CPU WUs and GPU WUs than just GPU on its own (in pure credit terms), to the extent that with GPU Projects that "pay" high credit rates (like Moo), its overall better not to crunch any CPU WUs.

If the CPU WUs are run because of the science, then no issue obviously, but if its all done for credit motivation, dont run any CPU WUs when crunching Moo, and your overall credit output will be higher than if you did run CPUs as well as Moo GPU WUs.

Regards
Zy

There is a long standing bug in OpenCL applications that affects dual GPUs (either on one card or two single GPU cards). The bug grabs a complete CPU Core for each GPU running. There is nothing the Project can do about it - has to be fixed at the OpenCL/AMD/NVidia side of life.

That one has nothing todo with Philadelphias problem nor with the dnetc client(which was coded using ATI CAL/STREAM NOT openCL).

That one -> dnetc518-win32-x86-stream.exe is the CPU app and of course it'll utilize the CPU at 100%.

@Philadelphia, just make sure to disable receiving CPU tasks in your account settings and that will solve the issue.

---

Join BOINC United now!

That one has nothing todo with Philadelphias problem nor with the dnetc client(which was coded using ATI CAL/STREAM NOT openCL).

That one -> dnetc518-win32-x86-stream.exe is the CPU app and of course it'll utilize the CPU at 100%.

@Philadelphia, just make sure to disable receiving CPU tasks in your account settings and that will solve the issue.

I changed the settings to these settings. Ok, or modify?

Thanks.

That one has nothing todo with Philadelphias problem nor with the dnetc client(which was coded using ATI CAL/STREAM NOT openCL).

That one -> dnetc518-win32-x86-stream.exe is the CPU app and of course it'll utilize the CPU at 100%.

@Philadelphia, just make sure to disable receiving CPU tasks in your account settings and that will solve the issue.

I changed the settings to these settings. Ok, or modify?

Thanks.

Hah! We see only our own settings, not yours, with that URL. Just follow Cunch3er's instructions and you'll be fine. ;)

If you want to see results right away, delete any tasks with that particular app.

---

Reno, NV
Team SETI.USA

That one has nothing todo with Philadelphias problem nor with the dnetc client(which was coded using ATI CAL/STREAM NOT openCL).

That one -> dnetc518-win32-x86-stream.exe is the CPU app and of course it'll utilize the CPU at 100%.

@Philadelphia, just make sure to disable receiving CPU tasks in your account settings and that will solve the issue.

I changed the settings to these settings. Ok, or modify?

Thanks.

Hah! We see only our own settings, not yours, with that URL. Just follow Cunch3er's instructions and you'll be fine. ;)

If you want to see results right away, delete any tasks with that particular app.

Gotcha. The second 5870 is out at the moment to make a dummy plug. I drove right by a Radio Shack and forgot to stop. :(

Thanks for everyone's help!

Dan/Philly

Hi Crunch3r,
I setup a HD4670 AGP using driver 11.11. gpuz_hd4670
The app uses 95% of CPU
hd4670_AGP_cpuload_dnetc518-win32-x86-stream
I got still one wu for cpu and cancelled it already.
In my preferences I set work for ATI only, no CPU. Nothing changed ...
Have a look on my hostid=6886
Any help appreciated.

heinz

Hi Crunch3r,
I setup a HD4670 AGP using driver 11.11. gpuz_hd4670
The app uses 95% of CPU
hd4670_AGP_cpuload_dnetc518-win32-x86-stream
I got still one wu for cpu and cancelled it already.
In my preferences I set work for ATI only, no CPU. Nothing changed ...
Have a look on my hostid=6886
Any help appreciated.

heinz

You have a single CPU with a single core and 1 GB RAM.

If you are running another project on this computer as well as MOO then you are probably running out of system resources.
The GPU then does a lot of CPU requests trying to get CPU time and some system Memory in order to help process a GPU work unit.
If the GPU can't get what it wants then it sits there waiting increasing your run time.

This is not gospel and could easily be wrong but it is a possibility.

Conan

---

dont run any CPU WUs when crunching Moo,

just make sure to disable receiving CPU tasks in your account settings and that will solve the issue

Read this thread because I don't seem to be able to get Moo! CPU preferences to work as I want i.e., Moo! CPU tasks just do their own thing irrespective of any preferences (BOINC, project & local).
The above quotes fill me with not much hope.

For example, a PC running Windows XP Pro SP3, 32-bit with one CPU and HT enabled to give me two logical cores:-
I set (all) crunching preferences to 100% of the processors or 2 tasks at a time & 50% of the time.
Two Moo! tasks will run ... but 100% of the time of both logical cores.
The same happens on a different PC with two physical cores, no HT, different make of processor, different (Windows 7 Home Premium SP1, 64-bit) OS.

Seems like a fundamental problem.

Question:- how do I get Moo! to work as I want it to?

---

oops duplicate message now deleted- pressed "Post" twice, sorry

dont run any CPU WUs when crunching Moo,

just make sure to disable receiving CPU tasks in your account settings and that will solve the issue

Read this thread because I don't seem to be able to get Moo! CPU preferences to work as I want i.e., Moo! CPU tasks just do their own thing irrespective of any preferences (BOINC, project & local).
The above quotes fill me with not much hope.

For example, a PC running Windows XP Pro SP3, 32-bit with one CPU and HT enabled to give me two logical cores:-
I set (all) crunching preferences to 100% of the processors or 2 tasks at a time & 50% of the time.
Two Moo! tasks will run ... but 100% of the time of both logical cores.
The same happens on a different PC with two physical cores, no HT, different make of processor, different (Windows 7 Home Premium SP1, 64-bit) OS.

Seems like a fundamental problem.

Question:- how do I get Moo! to work as I want it to?

I had the same problem and I solved it. After I installed the catalyst 12.1 CPU usage is 1-2%.
OS win7 64bit, gpu 6950 and 4770.

Thanks very much Semtex for the reply.

My post concerns only CPU tasks.

Ray.
(But after I read your reply I also noticed that every Moo GPU task also swamps my HT CPU of an ADDITIONAL up to and mainly near 50% effort. So Not Good. Maybe that is fixed with a CCC update but I'm tied to AGP on my main PC and AMD don't yet/ever will do 12.1 for AGP. FWIW Collatz, Milkyway & Cosmology behave impeccably, same PC, same preferances i.e., Cosmology @ 25% CPU load per task concurrent with Collatz @ imperceptable CPU load. These projects clearly do not require a CCC upgrade so ... how do I get Moo! to work as I want it to?)

---

See ...
http://www.gti-r.com/MooGPUTaskRobs50PercentOfMyCPUa.jpg
and
http://www.gti-r.com/MooGPUTaskRobs50PercentOfMyCPUb.jpg

When I have time in the next 24 hours I will also link screenshots of MOO CPU tasks exceeding preferences as originally described (it's late here in the UK)

Ray

My post concerns only CPU tasks.

If you don't mind, could you create a new thread for the CPU tasks not respecting BOINC preferences? That's a different problem and something I could probably do something with.

(But after I read your reply I also noticed that every Moo GPU task also swamps my HT CPU of an ADDITIONAL up to and mainly near 50% effort. So Not Good.

There has been various reasons why our Windows GPU tasks use too much CPU when they communicate with the GPU to give it things to crunch through.

Certain ATI driver version have bugs in them that seem to affect us this way (downgraded to 11.6 myself to fix this). This can also happen if the card is overheating or if BOINC Client keeps interrupting our crunching, both of which make us communicate with the card more and thus use more CPU. I believe some people have had success when they changed the selected core (in the project preferences) used.

Hmm, I should probably create a FAQ type posting about this Win GPU high-CPU problem since it's a complicated problem affected by many users. :)

-w

Thanks Teemu - as ever, one never knows whether "it's just me, I've set something wrong" or it is a general issue. Which this GPU issue seems to be. A FAQ type posting would be good.

I have started a new thread as suggested for the CPU-only issue.

Ray
(AMD/ATI's CCC appears to hold many pitfalls:- I run one PC where all the versions of GPU-Z after 0.2.4 fail on all versions of CCC after 11.4. Fond memories of Windows 3.11)