Forum > GPU crunching
CUDA_V12_app
Lord Asmodeus:
OK, I can do it step by step. It's a little bit confusing. The days of the simple optis are long gone ;D
Raistmer:
--- Quote from: Lord Asmodeus on 29 Jul 2009, 04:07:40 pm ---OK, I can do it step by step. It's a little bit confusing. The days of the simple optis are long gone ;D
--- End quote ---
Did you use installer or downloaded V12 from some other source?
Sutaru Tsureku:
@ Lord Asmodeus
DL the Installer for your OS here:
http://lunatics.kwsn.net/index.php?module=Downloads;catd=9
If you installed, the CUDA app work fine.
Min. nVIDIA_driver_185.85
If you would like to have a little booster take the newest nVIDIA_driver_190.38 and the CUDA_V2.3 .dll's.. ~ 30 % faster.
http://lunatics.kwsn.net/12-gpu-crunching/latest-nvidiadriver-and-cudaversion.0.html
Sutaru Tsureku:
Because of the priority of the CUDA_V12_app.
IIRC, in past with all stock the priority of the apps:
CPU tasks 'low'
GPU tasks 'lower than normal'
And this all the time.
Now with the opt._CUDA_app:
CPU tasks 'low'
GPU tasks 'low'*
[* at the CUDA WU start this priority is for ~ 5 sec. to 'lower than normal'. After down to 'low'.]
The priority is shown wrong in TaskManager and the opt._CUDA_app is all the time like the stock_CUDA_app at 'lower than normal'?
If, why the priority isn't shown correct all the time with the opt._CUDA_app?
Thanks! :)
Jason G:
--- Quote from: Sutaru Tsureku on 29 Jul 2009, 08:20:23 pm ---The priority is shown wrong in TaskManager and the CUDA WU is all the time like the stock app at 'lower than normal'?
If, why the priority isn't shown correct all the time with the opt. CUDA app?
--- End quote ---
Hi Sutaru, the "Process Priority" shown by task manager is controlled/set by Boinc when it launches the app. What is manipulated inside the GPU app is the priority of the internal 'worker thread', which apparently was set too low in the original code. To see/manipulate individual thread priorities, you would need to use 'Process Explorer' or similar tool. My understanding, though it's Raistmer's mod so he can explain his reasoning better, is the worker thread is put at a slightly higher priority than before, which ensures certain types of stalls & such won't occur as often, since kernel operations & transfers can be time sensitive, so should be allowed to complete before interruptions from the controlling thread. The need for this may or may not be reduced in the future.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version