Forum > GPU crunching

Driver, application and VRAM requirement?

<< < (6/13) > >>

Richard Haselgrove:
One thing I've noticed from the results you've reported recently (pending, valid) is that your elapsed time seems to be ~2.5 times your CPU time, for both CPU and (nominal) GPU tasks. That ratio feels high, even for three tasks (2 x CPU, 1 x fallback) running on two cores. Back in May (main board message 1009028), elapsed and CPU timings were within 400 seconds. Feels like something is eating CPU cycles, more than just browsing would do. Anything in Task Manager?

Raistmer:

--- Quote from: Miep on 24 Jul 2010, 09:00:50 am ---@Raistmer context creation? sorry you lost me - you want me to check GPU usage under different scenarios, to see what influences the components have? ok, I'll try.
btw ther's a 'H' missing in your 'IMO' ;)


--- End quote ---
LoL, that opinion wasn't "Humble" one it seems ;D
In addition some BOINC versions made check of free GPU memory. And not only at startup. So, if driver version fallbackwill not help, BOINC version fallback still worth to try.
Your priority should be to get stable GPU processing w/o fallback mode and then, 2.2 or 2.3 CUDA DLLs versions if possible. It will give nice GPU speed boost, much bigger then any new drivers or BOINCs.

Miep:
I thought I mentioned I was using TThrottle to keep the temepratures down. (and I still think its running way too hot)
Now with CPU only it is at about 50-60%, when the GPU generates extra heat they both get around 40% - would have to check the graphs after inactivity, doesn't seem to get logged.

this task ran partly on 6.08 and on V12 - no fallback. :)

I can give the 2.2 dll another try.

Richard Haselgrove:

--- Quote from: Raistmer on 24 Jul 2010, 09:48:53 am ---
In addition some BOINC versions made check of free GPU memory. And not only at startup. So, if driver version fallbackwill not help, BOINC version fallback still worth to try.
Your priority should be to get stable GPU processing w/o fallback mode and then, 2.2 or 2.3 CUDA DLLs versions if possible. It will give nice GPU speed boost, much bigger then any new drivers or BOINCs.


--- End quote ---

IIRC, when that code is active, BOINC just suspends the GPU app entirely, and periodically retests to see if the free GPU memory available has gone back up to a high enough level to allow the app to run again. Shouldn't crash anything, certainly can't influence the internal workings of the app to induce CPU fallback. And I don't think it would work under Anonymous Platform anyway. BOINC would need to know how much free VRAM the app requires: it can't get that from the server under A_P, and we've never tested or advised putting it into app_info.xml (and it's not in the specifications for A_P, though I suspect the documentation is incomplete: Gary Roberts at Einstein has certainly got more to work than the documentation says is supported).

Raistmer:
Richard, could you confirm that BOINC itself doesn't take GPU memory?
If not all details when and how it does anything not matter much. If GPU memory reduced it can influence on science app.

Navigation

[0] Message Index

[#] Next page

[*] Previous page