Hi, atrous (contrast equalizer) is quite heavy on hardware and needs a lot of memory to store the intermediate wavelets scales. I remember having the same issue on my previous laptop (GPU Nvidia 635M, 2 GB too) with certain updates of the driver.
Maybe you could try to decrease the memory headroom (opencl_memory_headroom=150) or don't cache modules output (opencl_synch_cache=false). Good luck, Aurélien. Le 09/11/2019 à 19:07, KOVÁCS István a écrit : > Hi, > > I think it's a user's question, but quite technical and with the dev > version, so I'm posting it here. > I've been using darktable since the 1.x days, maybe longer. I have an > ancient Core2 Duo machine with just 4 GB of RAM and an NVidia GTX 650 > with 2 GB onboard. > For that reason, I have used the instructions for 32-bit systems, even > though I run 64-bit Linux > (https://darktable.gitlab.io/doc/en/special_topics_chapter.html#darktable_and_memory_32bit). > Namely: > worker_threads=1 > cache_memory=268435456 > host_memory_limit=500 > opencl_memory_headroom=600 > opencl_memory_requirement=600 > singlebuffer_limit=8 > > However, no matter what I do (e.g. increasing/decreasing opencl memory > headroom and requirement), I keep getting '[opencl_atrous] couldn't > enqueue kernel! -4' with the version compiled from master. On the UI, > I get: "tiling failed for module 'atrous'. output may be garbled". At > the console: > 10.892248 [opencl memory] device 0: 0 bytes (0.0 MB) in use > 10.893898 [default_process_tiling_cl_ptp] use tiling on module > 'atrous' for image with full size 5668 x 2160 > 10.893911 [default_process_tiling_cl_ptp] (3 x 1) tiles with max > dimensions 3836 x 2160 and overlap 512 > 10.893922 [default_process_tiling_cl_ptp] tile (0, 0) with 3836 x 2160 > at origin [0, 0] > 10.893938 [opencl memory] device 0: 132572160 bytes (126.4 MB) in use > 10.893951 [opencl memory] device 0: 265144320 bytes (252.9 MB) in use > 10.955908 [opencl memory] device 0: 265144420 bytes (252.9 MB) in use > 10.955952 [opencl memory] device 0: 397716580 bytes (379.3 MB) in use > 10.955965 [opencl memory] device 0: 530288740 bytes (505.7 MB) in use > 10.955976 [opencl memory] device 0: 662860900 bytes (632.2 MB) in use > 10.955989 [opencl memory] device 0: 795433060 bytes (758.6 MB) in use > 10.956001 [opencl memory] device 0: 928005220 bytes (885.0 MB) in use > 10.956013 [opencl memory] device 0: 1060577380 bytes (1011.4 MB) in use > 10.956024 [opencl memory] device 0: 1193149540 bytes (1137.9 MB) in use > 10.956036 [opencl memory] device 0: 1325721700 bytes (1264.3 MB) in use > 10.956047 [opencl memory] device 0: 1458293860 bytes (1390.7 MB) in use > 10.972430 [opencl memory] device 0: 1458293760 bytes (1390.7 MB) in use > 11.046771 [opencl memory] device 0: 1325721600 bytes (1264.3 MB) in use > 11.047131 [opencl memory] device 0: 1193149440 bytes (1137.9 MB) in use > 11.047477 [opencl memory] device 0: 1060577280 bytes (1011.4 MB) in use > 11.047821 [opencl memory] device 0: 928005120 bytes (885.0 MB) in use > 11.047842 [opencl memory] device 0: 795432960 bytes (758.6 MB) in use > 11.047860 [opencl memory] device 0: 662860800 bytes (632.2 MB) in use > 11.047876 [opencl memory] device 0: 530288640 bytes (505.7 MB) in use > 11.047893 [opencl memory] device 0: 397716480 bytes (379.3 MB) in use > 11.047910 [opencl memory] device 0: 265144320 bytes (252.9 MB) in use > 11.047926 [opencl_atrous] couldn't enqueue kernel! -4 > 11.047941 [opencl memory] device 0: 132572160 bytes (126.4 MB) in use > 11.048264 [opencl memory] device 0: 0 bytes (0.0 MB) in use > 11.048599 [default_process_tiling_opencl_ptp] couldn't run > process_cl() for module 'atrous' in tiling mode: 0 > 11.048618 [opencl_pixelpipe] could not run module 'atrous' on gpu. > falling back to cpu path > [mipmap_cache] thumbs fill 0.31/256.00 MB (0.12%) > [mipmap_cache] float fill 0/2 slots (0.00%) > [mipmap_cache] full fill 1/2 slots (50.00%) > [mipmap_cache] level | near match | miss | stand-in | fetches | total rq > [mipmap_cache] thumb | 13.64% | 13.64% | -nan% | 0.00% | 100.00% > [mipmap_cache] float | -nan% | -nan% | -nan% | 0.00% | 0.00% > [mipmap_cache] full | -nan% | -nan% | -nan% | 100.00% | 0.00% > > > [mipmap_cache] thumbs fill 0.31/256.00 MB (0.12%) > [mipmap_cache] float fill 0/2 slots (0.00%) > [mipmap_cache] full fill 1/2 slots (50.00%) > [mipmap_cache] level | near match | miss | stand-in | fetches | total rq > [mipmap_cache] thumb | 13.04% | 13.04% | -nan% | 0.00% | 100.00% > [mipmap_cache] float | -nan% | -nan% | -nan% | 0.00% | 0.00% > [mipmap_cache] full | -nan% | -nan% | -nan% | 100.00% | 0.00% > > > 58.728739 [dev_pixelpipe] took 47.965 secs (70.883 CPU) processed > `contrast equalizer' on CPU with tiling, blended on CPU [export] > 58.734511 [opencl memory] device 0: 195886080 bytes (186.8 MB) in use > 58.845848 [opencl memory] device 0: 391772160 bytes (373.6 MB) in use > 58.864929 [opencl memory] device 0: 195886080 bytes (186.8 MB) in use > 58.865473 [dev_pixelpipe] took 0.136 secs (0.101 CPU) processed `color > balance' on GPU, blended on GPU [export] > [...] > 64.683392 [opencl_profiling] profiling device 0 ('GeForce GTX 650'): > 64.683400 [opencl_profiling] spent 0.5573 seconds in [Write Image > (from host to device)] > 64.683405 [opencl_profiling] spent 0.6533 seconds in [Read Image > (from device to host)] > 64.683410 [opencl_profiling] spent 0.0295 seconds in colorin_unbound > 64.683415 [opencl_profiling] spent 0.0266 seconds in [Copy Image (on device)] > 64.683420 [opencl_profiling] spent 0.0791 seconds in eaw_decompose > 64.683425 [opencl_profiling] spent 0.0164 seconds in colorbalance_cdl > 64.683429 [opencl_profiling] spent 0.0165 seconds in > colorspaces_transform_lab_to_rgb_matrix > 64.683434 [opencl_profiling] spent 0.0162 seconds in filmicrgb_split > 64.683439 [opencl_profiling] spent 0.0268 seconds in colorout > 64.683447 [opencl_profiling] spent 1.4216 seconds totally in command > queue (with 1 event missing) > 64.683473 [dev_process_export] pixel pipeline processing took 55.546 > secs (79.220 CPU) > > Did I miss anything (other than a decade's worth of HW upgrades)? > > Thanks, > Kofa > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
