CUDA performance / GPU Utilisation |
![]() |
| log in |
Questions and Answers : Unix/Linux : CUDA performance / GPU Utilisation
| Author | Message |
|---|---|
|
So, I've CUDA working for s@h. | |
| ID: 946909 · | |
|
Effective? It completes WU's very quickly compared to the CPU. I guess that makes it effective. check your computer on your account page. the rac should be increasing. You might be able to adjust a system monitor to check your GPU usage. not sure since I dont know which flavor you are using | |
| ID: 946931 · | |
Effective? It completes WU's very quickly compared to the CPU. I guess that makes it effective. check your computer on your account page. the rac should be increasing. You might be able to adjust a system monitor to check your GPU usage. not sure since I dont know which flavor you are using... Well, the RAC does indeed appear to be rapidly increasing. Curiously however, the GPU lingers for long periods near it's baseline temperature of 41 deg C, often meanders around 44 deg C, and only briefly and occasionally hits near the max I've ever noticed at about 50 deg C. Are any of the lunatics toying with pipelining multiple WUs through but phased so that the GPU is more highly and more consistently utilised?... ;-) The nVidia console shows the fan speed and temperature, and I have the "power mizer" set to "performance". The system tools has some very nice displays to show all manner of system stuff including some very pretty graphs for just about everything except the GPU. So... There appears to be no obvious tool to show what utilisation is being achieved for the GPU. Other than to try to deduce something from the WU RAC... Aside: In the s@h app_info.xml, there is: <plan_class>cuda</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> How is the ncpus used? They were set to "0.44". I've just made a guess towards what I actually see from "top" whereby s@h is taking less than 1% CPU time. Happy crunchin', Martin Mandriva 2010 x86_64 Boinc 6.10.17 ____________ Mandriva Linux A user friendly OS! See new freedom Mageia2 The Future is what We make IT (GPLv3) | |
| ID: 947943 · | |
|
The s@h GPU app is now laying idle for periods after having run continuously for many hours. | |
| ID: 948085 · | |
|
Yes, same way as your CPU can go idle on a small resource share. There's only one resource share, one DCF, one debt per project. So when there's now debt gathered by the GPU, BOINC will do other projects first until that debt is gone. | |
| ID: 948089 · | |
Yes, same way as your CPU can go idle on a small resource share. There's only one resource share, one DCF, one debt per project. So when there's now debt gathered by the GPU, BOINC will do other projects first until that debt is gone. Except... In this case, there are no other projects using the GPU. Also, s@h's share of the CPU is set at about x5 or much more than the actual CPU time being used... So the GPU goes idle if other projects do not use up their GPU share? Happy crunchin', Martin ____________ Mandriva Linux A user friendly OS! See new freedom Mageia2 The Future is what We make IT (GPLv3) | |
| ID: 948095 · | |
Except.. That doesn't matter. You only have one debt, which is used for all, be it if you use only GPU, only CPU, or both. Go into debt as opposed to the other projects you are attached to and Seti will not request more work until that debt is gone. So you probably still have work for the CPU, it just won't request any more work at this moment for either. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
| ID: 948110 · | |
Questions and Answers : Unix/Linux : CUDA performance / GPU Utilisation
| Copyright © 2013 University of California |