Forum > GPU crunching

Driver, application and VRAM requirement?

<< < (2/13) > >>

Raistmer:
no need to red those dumps further. It's clear that memory allocation failed. AFAIK last GPU-Z shows memory usage for nVidia cards (no such service for ATI GPUs still). Maybe you can see how much GPU memory in use before running CUDA MB with this tool?

Miep:
OK.
So GPU-Z 0.4.4 reports 104MB used. Erm. Not good. A bit of tweaking (appareance to Basic and colours to 16bit) brought that down to 19 (oh and the windows fix to temporarily disable .lnk and .pif not sure if that has an impact).
Still not enough. :(

While I was looking at client_state I noticed

--- Code: --- Cuda error 'cudaMalloc((void**) &dev_GaussFitResults' in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcceleration.cu' in line 314 : out of memory.

setiathome_CUDA: CUDA runtime ERROR in device memory allocation (Step 1 of 3). Falling back to HOST CPU processing...
--- End code ---

even on the WUs that had (from a users perspective) run error free.
?!
So, what's it doing then? It does put load on the GPU after all?
I'll run with more free memory and see if that clears up...

Raistmer:
No, it performs fallback to CPU and not using GPU at all if you see listed message. It's slowest way to do seti task actually :) Better disable GPU processing completely then (if you can't free more memory for app).
Another way is to fallback to older CUDA DLLs (like 2.2 or even older) they have slower cuFFT but require less memory. That way will be still much better than CPU fallback mode.

Jason G:

--- Quote from: Raistmer on 21 Jul 2010, 04:28:05 pm --- It's slowest way to do seti task actually :)
--- End quote ---
No it isn't.  Asking my dog to process tasks is much slower. He hasn't returned a valid result yet  :o

Miep:
If it was doing just that, fine (not by cruching standards, but by 'I know what it's doing').

But how do you then explain
a) load on the GPU - from the heat generated that is. I'll run with GPU-Z in the background over night and see if iit shows load.
b) crunching times - well hard to say actually CPU is ak_v8b_win_ssse3x.exe and ap_5.05r409_sse.exe respectively GPU is 6.08 stock.
    and I'm getting 1h50' avarage for shorties on GPU and 1h30' on CPU
   When I was running both on stock GPU used to take about 1/3 of CPU - and besides the driver I've not conciously changed the setup.
[times are not really comparable though, I'm still finetuning how hot I allow CPU and GPU to get, while not having them throttled into oblivion]
c) both CPU cores are on approximately the same times as without GPU tasks. (same throughput)
d) shouldn't then a cpu core get taken over? I still get 3 tasks running.

So, from all I can tell at least part of it uses the GPU.

I don't think I've returned any of those tasks yet, so I don't know if they validate. Old setup used to, but as there was never any reason to check stderr I've no idea if it was showing
the same behaviour.

Navigation

[0] Message Index

[#] Next page

[*] Previous page