GPU WUs use more CPU

Message boards : Number crunching : GPU WUs use more CPU
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile [B^S] Dimitrij
Volunteer tester

Send message
Joined: 6 Nov 04
Posts: 3
Credit: 849,921
RAC: 0
Germany
Message 1204016 - Posted: 9 Mar 2012, 4:30:54 UTC

hi there,

i need some help/explanation: i recently discovered that the gpu-WUs for my nvidia 220 GT take a lot longer then normal. They also use 100% CPU according to the task-manager and not the indicated 0.14 % CPU.

anyone got a solution to this problem? thanks in advance. me specs are:
WIN7 64bit, always newest drivers for hardware, newest boinc client etc.

ID: 1204016 · Report as offensive
Profile Gatekeeper
Avatar

Send message
Joined: 14 Jul 04
Posts: 887
Credit: 176,479,616
RAC: 0
United States
Message 1204021 - Posted: 9 Mar 2012, 5:02:45 UTC - in response to Message 1204016.  
Last modified: 9 Mar 2012, 5:03:24 UTC

hi there,

i need some help/explanation: i recently discovered that the gpu-WUs for my nvidia 220 GT take a lot longer then normal. They also use 100% CPU according to the task-manager and not the indicated 0.14 % CPU.

anyone got a solution to this problem? thanks in advance. me specs are:
WIN7 64bit, always newest drivers for hardware, newest boinc client etc.


Seti cannot use your GPU. Here's the relevant lines from a completed WU's log:

"setiathome_CUDA: device 1 is emulation device and should not be used, supports 9999.9999
setiathome_CUDA: CUDA Device 1 specified, checking...
Device cannot be used
SETI@home NOT using CUDA, falling back on host CPU processing"

Since Seti can't use the GPU, it "falls back" and runs the unit on a CPU core.

Someone with some program/error message knowledge could probably offer you a more detailed explanation of the error.
ID: 1204021 · Report as offensive
Profile [B^S] Dimitrij
Volunteer tester

Send message
Joined: 6 Nov 04
Posts: 3
Credit: 849,921
RAC: 0
Germany
Message 1204023 - Posted: 9 Mar 2012, 5:10:40 UTC - in response to Message 1204021.  

thanks for the answer, that's an explanation. but since it worked before i want an answer if something changed from the seti-side. otherwise i will probably fall back to older drivers.
ID: 1204023 · Report as offensive
Blake Bonkofsky
Volunteer tester
Avatar

Send message
Joined: 29 Dec 99
Posts: 617
Credit: 46,383,149
RAC: 0
United States
Message 1204031 - Posted: 9 Mar 2012, 5:52:35 UTC - in response to Message 1204028.  

Without digging too deep, this is probably the same problem others have reported regarding the 295 drivers. Did you recently upgrade drivers?
ID: 1204031 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1204078 - Posted: 9 Mar 2012, 8:43:34 UTC - in response to Message 1204016.  

See this thread for the reason why:

Error while computing

Claggy
ID: 1204078 · Report as offensive
Profile [B^S] Dimitrij
Volunteer tester

Send message
Joined: 6 Nov 04
Posts: 3
Credit: 849,921
RAC: 0
Germany
Message 1204140 - Posted: 9 Mar 2012, 14:21:48 UTC

thanks everyone. YES, i recently updated drivers and in retrospect it was probably the time when the problem occured. i try the workaround from the other thread and -if not working- downgrade the drivers.
ID: 1204140 · Report as offensive

Message boards : Number crunching : GPU WUs use more CPU


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.