Yes, basically the defaults work well! But as long as I don’t use openCL tuning I don’t have any probs. I did have resources set to large previously, I might go back to that. I need to check if it makes a difference (now that I know how😀)
Try the new build to see if improved your issue. Im not sure it will.
Will do! Might be in a day or two though… A bit busy atm
I still get :
[opencl_lock_device] reached opencl_mandatory_timeout trying to lock mandatory device, fallback to CPU
even with the new build. Haven’t seen any performance hit though
If there are no other errors, and you see this while working in the darkroom, this can be the consequence of what is discussed here:
Ok I think I understand now.
With a very fast GPU that you want to use for intensive DorS iterations, probably best to set the timeout high (600 seems to work for me)
But one more question, where do you set the dt_opencl_update_priorities to find out if my fast GPU makes any difference for preview, thumbs or preview2?
in my config file , I have
opencl_device_priority=/!0,///!0,*
in the log file
dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 1 1 1 1 1
I think that’s good. Now you can make measurements. 
1 Like