Forum > GPU crunching
Modified SETI MB CUDA + opt AP package for full GPU utilization
perryjay:
Wait! Are you saying they are thinking about doing away with credits? But I still don't have enough for my toaster! :(
Archangel999:
--- Quote from: Raistmer on 13 Jan 2009, 03:43:27 pm ---
--- Quote from: Archangel999 on 13 Jan 2009, 03:42:01 pm ---use mb_r396 mode with my windows xp x64 and all is ok :) no more crash and errors :)
--- End quote ---
396 is outdated now. Use 400 instead.
--- End quote ---
thanks but i will use 396 because it is ok for me ;)
Raistmer:
--- Quote from: Archangel999 on 13 Jan 2009, 04:27:14 pm ---
--- Quote from: Raistmer on 13 Jan 2009, 03:43:27 pm ---
--- Quote from: Archangel999 on 13 Jan 2009, 03:42:01 pm ---use mb_r396 mode with my windows xp x64 and all is ok :) no more crash and errors :)
--- End quote ---
396 is outdated now. Use 400 instead.
--- End quote ---
thanks but i will use 396 because it is ok for me ;)
--- End quote ---
It will be Ok just until new bunch of tasks arraives :)
Josef W. Segur:
--- Quote from: Raistmer on 13 Jan 2009, 03:44:11 pm ---About Vista's driver restart:
The default timeout period in Windows Vista is 2 seconds.
http://www.microsoft.com:80/whdc/device/display/wddm_timeout.mspx
--- End quote ---
Yeah, and here's what David Anderson is thinking of doing:
--- Quote ---From: David Anderson <davea@ssl.berkeley.edu>
Cc: boinc_alpha@ssl.berkeley.edu
To: BoincSpy Administrator <boinc_spy@telus.net>
Date: Sun, 11 Jan 2009 21:26:37 -0800
Subject: Re: [boinc_alpha] CUDA Blue Screen of death.
Message: 3
I've seen this also.
It's not related to driver version.
According to NVIDIA engineers,
if a GPU driver request doesn't complete in 2 seconds,
Windows assumes it's hung, and crashes.
Apparently the SETI@home/CUDA app does something that
sometimes takes > 2 secs on slow GPUs.
The NVIDIA people didn't have a fix or workaround for this.
So I'm going to change the server so that it won't send
CUDA jobs to GPUs slower than 60 GFLOPS
(I'm not sure this is the magic number,
but on my machine the GPU is 50 GFLOPS,
computed as clockRate * multiProcessorCount * 2,857).
-- David
--- End quote ---
From a comment somewhere in the BOINC sources, his board is a Quadro FX 3700.
Joe
Raistmer:
Wrong decision IMHO.
1) only some range of tasks suffer from this trouble - so no need to restrict whole host from processing.
2) it possible to repair application or at least tofall back to CPU version on these affected tasks.
That is - no intervntion on server side is required, at least in form of restriction whole host from getting CUDA work.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version