Cuda tasks not using GPU |
![]() |
| log in |
Message boards : Number crunching : Cuda tasks not using GPU
| Author | Message |
|---|---|
|
I have a Dell M6300 laptop (http://setiathome.berkeley.edu/show_host_detail.php?hostid=6840544) with an Core 2 Extreme and an Nvidia Quadro 1600M graphics processor. I just installed Windows 8 on it and installed the latest cuda drivers for it. I then downloaded new SETI tasks and I see that one of the tasks which is running is supposed to be utilizing the GPU, but it's utilizing ~50% of the main processor and according to GPU Shark (which is the GPU utilization task that I downloaded), the GPU is running a 0% utilization. | |
| ID: 1308532 · | |
|
You're run out of GPU memory: | |
| ID: 1308534 · | |
|
Thanks for the info. I switched themes, basically shutting off Aero & got a lot of memory back. However, now I get the following. Is this just a fools errand to try to use this GPU? | |
| ID: 1308553 · | |
Thanks for the info. I switched themes, basically shutting off Aero & got a lot of memory back. However, now I get the following. Is this just a fools errand to try to use this GPU? If you can be patient, the servers ought to eventually send some GPU tasks to be done with the 6.08 CUDA application, which is much more suitable for a GPU with 256MB VRAM. When the 6.09 CUDA23 application was first available, BOINC's method of deciding whether it was suitable for a given GPU would have prohibited sending that work to your GPU because it has less than 384MB of VRAM. To make a change then required editing a source file and recompiling the server code. More recently BOINC has a revised method which is controlled by a separate XML file. That seems to be buggy, but is so obviously a better approach that the project has adopted it. When more pressing issues are solved, they'll get it debugged, I'm sure. The increased memory usage of 6.09 is IIRC mainly because of the revised cufft.dll and that also provides a significant boost in productivity on GPUs which can use it. It might be possible on your GPU with even more changes to free up VRAM, perhaps dropping to 16 bit color, etc. That may be more than you want to do. Perhaps the sensible thing to do is to simply abort any CUDA23 work the servers assign, so a resend can go promptly to another host. Even with 6.08, the GPU ought to provide a significant improvement in productivity over doing only CPU work. But if the project has to go to only WUs with 4 times as much data as indicated in the News, GPUs with only 256MB will probably no longer be usable. That's months away, in the meantime your GPU might do a considerable amount of work. Joe | |
| ID: 1308587 · | |
|
download tthrottle and see what it says, also temp monitoring and throttling can save you a cpu or gpu perchase in the near future seti can run them hot.also not all client use opencl or cuda and with no installer available from Lunatics site right now installing optimized clients can be a pain hang in there some astropulse | |
| ID: 1308766 · | |
|
fft is fast Fourier transform might try the math library s at | |
| ID: 1308768 · | |
|
This is actually an old machine of mine that I'm giving to my 91yo dad, so I'm not going to worry about this. I just installed the GPU drivers for desktop and new laptop, so we'll see how those go. Thanks for the help! Hopefully I won't need it with my systems. | |
| ID: 1308791 · | |
|
the cpu likely does not support the more advanced modes necessary to run new optimized clients but an older one might work. | |
| ID: 1308867 · | |
|
I just got a nvidia GeForce GTX 650 with 2 GB of memory & installed it on a core i7 machine running Windows 8. All of my tasks are now aborting immediately with the following errors. The card has plenty of free memory and is running cool. Any ideas? <core_client_version>7.0.28</core_client_version> ____________ | |
| ID: 1319375 · | |
|
Check the 2nd part ( 2) Kepler cards unsupported ) of this post out, http://setiathome.berkeley.edu/forum_thread.php?id=69735#1296126, as it maybe your problem. | |
| ID: 1319382 · | |
|
Thanks for the quick reply. As per the suggestions, I set the environment variable CUDA_GRID_SIZE_COMPAT to 1 and restarted BOINC and it's no longer aborting. | |
| ID: 1319415 · | |
|
edit app_info | |
| ID: 1319431 · | |
edit app_info He's using stock app...no app_info file. ____________ | |
| ID: 1319433 · | |
edit app_info So use app_config.xml instead: BOINC 7.0.40-42 and new app_config.xml (requires use of alpha-test version of BOINC) | |
| ID: 1319471 · | |
|
So where do I find this alpha version? | |
| ID: 1319480 · | |
So where do I find this alpha version? The easiest way is to get the links from the BOINC 7 Change Log and news thread. Edit: the following is for Anonymous Platform Users only: (But beware, because of a change in Boinc 7.0.32, where the internal flops value for the GPU was increased by times 10, all existing GPU work will be on the verge of going Maximum Time Exceeded, so finish any GPU work first prior to upgrading, new GPU work will be O.K} Claggy | |
| ID: 1319481 · | |
Message boards : Number crunching : Cuda tasks not using GPU
| Copyright © 2013 University of California |