here are some suggestions for configuring OpenCL for modern hardware. I own an AMD Radeon RX470 (8GB RAM). If you have a similar card, the settings will work for you too.
Here are the values I use in my ~/.config/darktable/darktablerc
opencl_async_pixelpipe=true
opencl_avoid_atomics=false
opencl_device_priority=*/!0,*/*/*
opencl_number_event_handles=250
opencl_scheduling_profile=very fast GPU
opencl_micro_nap=100
thru this discussion, I was just now experimenting with opencl_memory_requirement and bumped it up to 2048.
in this issue #2724 I said, the WB (for instance) getting vers smooth, when I grab the slider a second time.
Now with opencl_memory_requirement=2048 this effect disappears to the negative, means it remains sluggish, no matter how often I “re-grab”. Values from 512 to 1024 do behave like I described in that issue.
Can you conclude something out of this?
Edit 1
I did some benchmarking and also had "watch nvidia-smi " running. With opencl_memory_requirement=2048 opencl obviously switches off completely (in case that is documented somewhere, sorry, I did not see that)
Edit 2
O.k. I got reminded from darktable.org, opencl_memory_requirement means, that amount is to be present at least, so the card will be accepted. Anyhow I cannot understand, as merely 420MB are occupied by plasma, so 5,5GB should be available, why opencl gets switched of? From here, we are running OT, I guess…
I have not seen an official Neo release for Windows - as a result back when I submitted the patch that un-blacklisted Neo as a result of discoveries made as to the root cause of original failures (improper cache invalidation on driver updates), due to not having any testing done on Windows (and the most recent information being that failures had occurred), the blacklisting was ONLY removed for Linux platforms on which I (and a few others) could confirm that recent NEO drivers were working well.
A potential outstanding issue is that some distributions are packaging the drivers in such a way as to report a 1.0.0 version regardless of actual version, which may break cache invalidation. I was going to look into that but switched away from darktable for other reasons instead.
For Linux platforms, Intel provides status of whether the driver passed Khronos conformance tests at Releases · intel/compute-runtime · GitHub - no such testing artifacts are provided for Windows builds (and in fact Windows has no official releases.)
Hi! Did you experience some speedups during export? I’ve tried exporting with open CL active and entire system interface freeze. Plus I’ve not experienced any speedup, also with your settings.
Intel uhd 620 here