Could you please do a test for me:
Go to Index of /~sarunas/bench_raw/setubal and download setubal.orf and setubal.orf.xmp, Please note Firefox did not download the correct exetension name, if, rename it according to the size.
Check the right configuration, if Darktable can use all the available ressources. This setting can be a big difference in speed. I got the double speed with “large”.
Settings / processing / CPU - Memory / darktable resources: large
It took me weeks to find this out with my Intel B650. Compare No opencl with Intel B580 (Asrock Challenger) - #24 by linuxuser In this thread you can find also what I did with Ubuntu to get opencl working.
With the B580 I have now:
pixel pipeline processing took 1.415 secs
Of course this value never can be reached with an integrated gpu.
With my Beelink SER6 Max minipc, where I did not get opencl working, I get
pixel pipeline processing took 11.437 secs (Full log attached)
After everything is prepared please do:
darktable-cli setubal.orf setubal.orf.xmp test.jpg --core -d perf -d opencl
The interesting value is “pixel pipeline processing took” at the end of the log. Please attach the full log.
The question is, if it is noticeable faster than my SER6.
setubal-beelink.ser6.max.ryzen7,7735hs.32gb_resources.large-log.txt (4.5 KB)