Hi,

I have a weird opencl memory issue. I just got a new NVIDIA GFX 1050 Ti and 
wanted to do some benchmarking. I typically use the benchmarking which has been 
described several times here in this group as well. I run


darktable-cli bench.SRW test.jpg --core -d perf -d opencl 

and see how long pixpelpipe processing takes.

But this time I wanted to this with a bigger RAW. Something that is really 
stressing the GPU. SO I got RAW_CANON_EOS_5DS.CR2 from 
http://www.rawsamples.ch/raws/canon/RAW_CANON_EOS_5DS.CR2


darktable-cli RAW_CANON_EOS_5DS.CR2 --core -d perf -d opencl 
That works fine. NO memory issue.

Then I open the DT GUI and export a couple of my Canon 6D files. And this also 
works fine.

But then I go back to the commandline and try again with RAW_CANON_EOS_5DS.CR2 
and I get 

1,018442 [default_process_tiling_cl_ptp] use tiling on module 'denoiseprofile' 
for image with full size 8734 x 5856
1,018451 [default_process_tiling_cl_ptp] (2 x 1) tiles with max dimensions 8128 
x 5856 and overlap 8
1,018453 [default_process_tiling_cl_ptp] tile (0, 0) with 8128 x 5856 at origin 
[0, 0]
11,549347 [opencl_denoiseprofile] couldn't enqueue kernel! -4
11,553563 [default_process_tiling_opencl_ptp] couldn't run process_cl() for 
module 'denoiseprofile' in tiling mode: 0
11,553568 [opencl_pixelpipe] could not run module 'denoiseprofile' on gpu. 
falling back to cpu path


Can it be that the DT GUI is not releasing all the GPU memory and then the 
commandline fails? And the worst thing is that the system is not recovering 
from that. Even with bench.SRW which is a lot smaller it is not working 
anymore. The GPU memory is gone.

3# ll bench.SRW *.CR2
-rw-r--r--  1 matthias matthias 20453024 17. Jan 2017  bench.SRW
-rw-r--r--+ 1 matthias matthias 67127952 16. Feb 2017  RAW_CANON_EOS_5DS.CR2

Matthias

PS
I have set opencl_memory_headroom=400. But it does not help.

____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to