So who's running the SETI CUDA client then?

Soldato
Joined
13 Jan 2004
Posts
2,608
Location
Market Deeping
Probably not many, but I'm going to start highlighting users in the news that are using the S@H CUDA client, so a simple yes + username will suffice. You could also report your experience of it so far if you want, as this may help others to decide to take it up or not (not least of all me :D).

GPU user list (as of 06/02/2011)
Ba
Biffa
br83taylor
carbon8ed
Chasser
eggcup
FluffySheep
GrandMasterD
Grimgoth
halz
Jonathan Jeffrey Davis
k3v
kolala
loudbob
MadMaC
Marine Iguana
Mason-
Meridian
Odan
Pilgrim57
pnutty
ReaVerUK
Simon
the_running_man
ToxicTBag
wayne


Please note that any members that haven't shown any SETI activity for a month are removed from the list. Also, please help me maintain an up-to-date list by letting me know if you've started/stopped using the GPU app. :)
 
Last edited:
It's the power usage that's putting me off GPU crunching. My Q9550 - pushed to 3.4GHz - seems to have made its impression on the bill, so I don't really want to risk making it any more expensive. Shame, as they seem to crunch quite well...
 
Yes, in comparison to the D series chips I think they are more energy efficient, but the fact quad's been clocked from 2.8 to 3.4 - with an increase in vcore required - doesn't help matters. I might be wrong with the adverse affect on the 'leccy bill though, so don't quote me on anything - I have been leaving this on 24/7 a lot more than the P4 I had, which got too hot during summer to do that (and that was at stock with a decent cooler!).
 
I believe the VLAR WUs are renowned for taking a very long time to process for no extra benefit, so much so that people who find they're running them tend to abort them. By the 'autokill initialised' message I assume you're using the VlarKill driver, which automatically detects and aborts all VLAR WUs.

So as long as the normal CUDA WUs are being completed successfully there's no problem at your end.
 
Back
Top Bottom