Forum > GPU crunching
CUDA_V12_app
Sutaru Tsureku:
I used the Installer (unchecked MB/AP, checked only CUDA) and installed to a temporary - not to the setiathome.berkeley.edu - folder.
Then I took the CUDA_V12_app and the 3 .dll's .
And on my GPU cruncher work this app.. ;)
4 x OCed GTX260-216
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4789793
Hmm.. it's look like the CPU support time is like before with the latest CUDA_V11_app.
Current I can't look to the real wall clock time, because the tasks overview of the PCs are disabled at SETI@home.
In the description I read:
Build with smaller pulse find limit (2048), hoped to exhibit less issues on most nVidia Cards.
What does this mean?
Which GPUs are meant?
GTX260-216 ?
The CUDA_V12_app should be faster than the CUDA_V11_app ?
The CPU preparation time of the CUDA WUs are the same.
So the GPU calculation time is faster?
Thanks! :)
Jason G:
--- Quote from: Sutaru Tsureku on 18 Jul 2009, 12:06:53 pm ---...
In the description I read:
Build with smaller pulse find limit (2048), hoped to exhibit less issues on most nVidia Cards.
What does this mean?
Which GPUs are meant?
GTX260-216 ?
--- End quote ---
It turmed out to be all GPU cards tested so far. If you didn't get any display problems & laginess before, then it doesn't apply to you, no change willl be obvious. [Edit: Of course if you have no display plugged into the card, you wouldn't see any display problems either ;D]
--- Quote ---The CUDA_V12_app should be faster than the CUDA_V11_app ?
--- End quote ---
By some small amount only, depending on machine/card. That may or may not apply to your card, since it is already fast ;), and some small change in time might be hard to notice/measure.
--- Quote ---The CPU preparation time of the CUDA WUs are the same.
So the GPU calculation time is faster?
--- End quote ---
No, the preparation time should be shorter than V11. If not, then your CPU is too fast for you to tell the difference also. :D
So the changes may or may not have any effect at all on your card/system, which I would place in the category of 'ninja bastard' hardware, that will just go fast anyway. They are mostly directed at those of us whose machines used to become unusable for normal use.
Raistmer:
--- Quote from: Sutaru Tsureku on 18 Jul 2009, 12:06:53 pm ---Build with smaller pulse find limit (2048), hoped to exhibit less issues on most nVidia Cards.
--- End quote ---
It's part of internal app tuning leaked into public area :)
Only really slow (like 8300 if such card exists :) ) GPUs could have some problems with changes that governed by this value.
And yes, V12 could be slightly faster than V11. Mostly in VLAR area though. But VLAR processing too slow still so I recommend not to use CUDA MB apps to process VLAR tasks. Use rebranding instead.
Lord Asmodeus:
I switched from a V11 wich was working fine to V12, and my videos started freezing, it reminded me of the CPU optis a long time ago. How is that possible ?
I restored my backup and all is OK.
This was some weeks ago, I wil try the new nvidia/CUDA drivers and make another attempt at V12.
Raistmer:
--- Quote from: Lord Asmodeus on 29 Jul 2009, 03:44:48 pm ---I switched from a V11 wich was working fine to V12, and my videos started freezing, it reminded me of the CPU optis a long time ago. How is that possible ?
I restored my backup and all is OK.
This was some weeks ago, I wil try the new nvidia/CUDA drivers and make another attempt at V12.
--- End quote ---
then stay with V11, just update CUDA RT DLLs to 2.3
Navigation
[0] Message Index
[#] Next page
Go to full version