Forum > GPU crunching
Modified SETI MB CUDA + opt AP package for full GPU utilization
Richard Haselgrove:
--- Quote from: Josef W. Segur on 13 Jan 2009, 06:21:25 pm ---
Yeah, and here's what David Anderson is thinking of doing:
--- Quote ---...
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
--- End quote ---
That card has the same number of shaders (112) as my 9800GT (but costs six times as much - hehe).
I can't find a clock speed for it - but if I plug the shader clock for the 9800GT (1500 MHz) into the formula, I get 48 GFLOPS: seems like the right ballpark.
If they're going to set the limit 25% above a 9800GT, then GPU crunching is dead until the next generation of hardware.
alollini:
I try with V5a ... that seems to work
however I have still only 4 tasks running, that may be better with 5
if the overall performance is better with real_number_of_cores + 1
where do i enter this setup ? in what file ? what line ?
Raistmer:
--- Quote from: Haselgrove on 14 Jan 2009, 05:45:38 am ---
--- Quote from: Josef W. Segur on 13 Jan 2009, 06:21:25 pm ---
Yeah, and here's what David Anderson is thinking of doing:
--- Quote ---...
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
--- End quote ---
That card has the same number of shaders (112) as my 9800GT (but costs six times as much - hehe).
I can't find a clock speed for it - but if I plug the shader clock for the 9800GT (1500 MHz) into the formula, I get 48 GFLOPS: seems like the right ballpark.
If they're going to set the limit 25% above a 9800GT, then GPU crunching is dead until the next generation of hardware.
--- End quote ---
Sorry but I consider this approach as meaningless. We speak about doing SETI on Android platform, ON CELLPHONES (!!!) and throw away 50GFLOPs of power? Nonsense!
So, there will be custom builds that will work on all CUDA-enabled GPUs and will just abort VLARs as my current V5a/b do. Much better if true bug-fix will be developed than such inefficient workaround... Even falling back to CPU processing approach much better than this.
Raistmer:
--- Quote from: alollini on 14 Jan 2009, 05:52:08 am ---I try with V5a ... that seems to work
however I have still only 4 tasks running, that may be better with 5
if the overall performance is better with real_number_of_cores + 1
where do i enter this setup ? in what file ? what line ?
--- End quote ---
search for cc_config.xml file description. You need ncpus field.
I will add minimal cc_config.xml example to first post of this thread.
(done. You can take that sample and edit it if you have duo or single-core CPU instead of quad)
alexeft:
Hi Reistmer, thanks for all the effort you put (along with Crunch3r)
I'm using 5b and seems to work fine, had no crashes yet.
What I notice is that it goes slow at the beginning of the WU and then accelerates rapidly. Why is that so?
Also, the timer is totally wrong.
Thanks again!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version