Modified SETI MB CUDA + opt AP package for full GPU utilization

[The Grinch]

And continue with AK8 opt app for now.

Yes, i'm back on AK8, since there will be a stable one.

[Bluesilvergreen]

@Raistmer : Great Work!

But, how can I manage to run 4 + 1 with BOINC 6.4.5

I run Einstein and SETI Beta, but only 3 core's of my Q6600 running einstein and 1 core is almost idle, with the CUDA (8800GT) running.

Is it possible to run all 4 core's on einstein and the GPU on SETI Beta?


Anyway my system hangs from time to time for about 1 or 2 seconds. Should I increase the Memory-Bandwidth or try another CUDA-driver? When I stop the CUDA-App it all works fine without any hang up.

[Archangel999]

hi there yes my systemhangs too at exatly at the 15 second it is cuda problem or nvidia driver problem ...
The GPU need's cpu power so it can't do it for now

Best Regards
D.Draganov

[Radiohead]

This modified app WORKED ON 8800GTS 320MB!!!!!!!!

Standart SETI CUDA & GPUGRID:
12/11/2008 11:02:27 AM|SETI@home Beta Test|Scheduler request succeeded: got 0 new tasks
12/11/2008 11:02:27 AM|SETI@home Beta Test|Message from server: No work sent
12/11/2008 11:02:27 AM|SETI@home Beta Test|Message from server: SETI@home Enhanced is not available for your type of computer.


BEST!

[Raistmer]

1) About 4+1 mode. Look at my original post in this thread (btr, any modifications will be posted there, so it's wise to check head post time to time):
"
7) For best CPU and GPU usage I recommend to set number of processors available for BOINC to real_number_of_cores+1. This will mitigate current BOINC bug with CPU+CUDA scheduling and will allow fully load CPU and GPU.
"
2) 15 seconds problem still unsolved AFAIK. CUDA itself is not very mature technology still. For example, no CUDA kernel can't run more than 3 seconds continuosly or CUDA will crash. Maybe it's the case here.

3) it's definitely not my merit - to allow 8800GTS to tun Maybe it's consequence of app_info.xml use.... Maybe it's worth to recommend using of my package for other 8800 owners too...

[Richard Haselgrove]

Note that there was a server-side modification on the SETI Main project (and presumably Beta too, though I haven't seen any direct reports) about 21:30 UTC, Monday 22 December.

The minimum GPU memory requirement was reduced from 256MB to 254MB. Many of the smaller cards were reporting 255MB, so were switched from 'just too small' to 'just big enough'. That may well account for some users getting CUDA work, when it was 'not available for your [type of] computer' before.

[Raistmer]

Note that there was a server-side modification on the SETI Main project (and presumably Beta too, though I haven't seen any direct reports) about 21:30 UTC, Monday 22 December.

The minimum GPU memory requirement was reduced from 256MB to 254MB. Many of the smaller cards were reporting 255MB, so were switched from 'just too small' to 'just big enough'. That may well account for some users getting CUDA work, when it was 'not available for your [type of] computer' before.

Sure, very possible.

[Jason G]

Extended outage? Could be promising, ... or not 

[Jason G]

Okay, Pre-Release Boinc 6.5.0 *seems* to have fixed the +1 operation such that you don't need to set ncpus in cc_config anymore.  Well that's a start.

[..And base priority seems to be 'below normal' now too, might have fixed some of the pauses I was getting.  We'll see... That's two annoyances down!  ]

[Edit: Make that three! ... It seems that it's no longer suffering from oversubscription here either.  Will observe during new cuda task changeover to confirm.]

[Raistmer]

I tried 6.5 on x64. When boinc manager closes it closes only its windows. Process remains in memory and consumes full core (50% on duo).
I tried few times, after reboot after aborting process and so on - it always begins to consume CPU.
So I reverted to 6.4.5 that is official release now (at least for x64). It's pn Win2003 x64 host where I tried to run 2 CUDA- enabled GPUs simultaneously. 8500 ang 9400GT.
it seems only with 180.84 beta it will work w/o out of memory after each tak restart...

[Jason G]

LoL, crazy Boinc.

[lofty]

Hi Raistmer.

Tried your files today and when I restarted Boinc, although it recognised my CUDA abilities (I have an NVIDIA 8800GTX) I got computational errors on all my WUs. I don't think the problem was with the files, I suspect the problem is user related 

I have the latest version of Boinc (6.4.5) and after dloading your zip file I extracted the contents into my seti@home projects folder (C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu, the default location). Have I done the right thing or was something within the zip file supposed to go to, perhaps, the Boinc installation folder? Sorry to be the newb.

[Raistmer]

You did right thing, but maybe it's time to suspend CUDA indeed.
Look here:

http://setiathome.berkeley.edu/forum_thread.php?id=50937

[Raistmer]

To avoid further pollution of science database with wrong but passed validation results I suspend my mod distribution.
SETI CUDA should produce valid resutls or give computation error but not invalid "overflows" when go on large scale use. So, it should be repaired.

[lofty]

This is sad news indeed. I guess I will also suspend any further download of WUs. False results are not good: Bad science is worse than no science. I guess I will finish the WUs I have then return to my old optimized non-CUDA apps for the time being. Thanks for your response.

Merry christmas to crunchers everywhere!