Indeed Patrick, the default in the current version is: opencl_synch_cache=active module
The option I would advise to test for response time comfort during finetuning in a 2nd pass is: opencl_synch_cache=true. That is if it does not compromise too hard overall response time. Which is ok on my system/configuration. Met vriendelijke groet, Marc. > Op 20 nov. 2020 om 19:58 heeft Patrick Shanahan <[email protected]> het > volgende geschreven: > > * Marc Cabuy <[email protected]> [11-20-20 12:18]: >> Gian, >> >> >> >> Good to hear that. And yes I expect that that XEON processor will surely >> help (*). >> >> >> >> GPU performance can be further boosted by optimization of the opencl >> settings in file darktablerc. You can read about that in the darktable >> manual. >> >> >> >> But possibly adequate parameters for a nvidia gtx 1650 can be found in this >> thread: >> >> https://discuss.pixls.us/t/darktable-opencl-performance-with-nvidia-gtx1650-super/19965/17 >> as follows >> >> opencl_async_pixelpipe=true >> >> opencl_avoid_atomics=false >> >> opencl_mandatory_timeout=200 >> >> opencl_memory_headroom=1024 >> >> opencl_memory_requirement=2048 >> >> opencl_micro_nap=10 >> >> opencl_number_event_handles=1000 >> >> opencl_scheduling_profile=very fast GPU >> >> opencl_size_roundup=16 >> >> opencl_synch_cache=false >> >> opencl_use_cpu_devices=false >> >> opencl_use_pinned_memory=false >> >> >> >> I gained like 3 to 6 times better interactive response time for pictures >> with about 25 to 30 modules activated, by tuning these parameters on my GPU >> close to these values. >> >> >> >> Further I also have put opencl_synch_cache=true. If that doesn’t penalize >> general response time too much, it gives the advantage of better response >> when reviewing/finetuning module parameters further in a 2nd pass even with >> “denoise profiled” activated. That’s typical for my workflow. >> >> >> >> Regards, >> >> Marc. >> >> >> >> (*) But I am not an expert, since I use dt only since 6 months on an >> off-the-shelve overconfigured pseudo-gaming laptop from the MSI Creator >> series that I bought after my dual core I7 Acer laptop died. >> >> >> >> >> >> Van: GianLuca Sarto [mailto:[email protected]] >> Verzonden: vrijdag 20 november 2020 13:30 >> Aan: [email protected] >> Onderwerp: Re: [darktable-user] Tone equaliser and response time during >> zooming/panning on 4K display (dt 3.2.1-Windows 10) >> >> >> >> Marc, >> >> >> >> thank you very much for your warning! >> >> >> >> As you see, the first step is done, and I can see a huge improvement in >> browsing through the lighttable with the GTX 1650. >> >> >> >> I was wondering too if it is worth to go to 4K, I wouldn't like to go back >> to square one, performance wise. >> >> >> >> Maybe 2560x1440 is the wise compromise, and I save a lot of money: I do not >> really feel constraint at 1920x1200, I was suffering more for the slow >> paging. >> >> >> >> In the next few days I should receive a second hand Xeon E3, that might >> boost further the overall performance. >> >> >> >> -Gian >> >> >> >> >> >> On 20/11/20 12:53, Marc Cabuy wrote: >> >> Gian-Luca, >> >> >> >> Just a little warning about purchasing a 4K display. You indeed will need a >> good GPU. But still there is (or are) module(s) that are fully cpu-bound. >> That’s the case with tone equaliser. Interactive response when zooming and >> panning in the darkroom may suffer from poor response time on a 4K display >> (3840x2160) when you have a tone equaliser module activated in the module >> stack. That’s my experience with dt 3.2.1 for Windows on my 16mp pictures. >> That issue is not existing that much on my WQHD display (2560x1440) or >> almost not on a HD display (1920x1080). >> >> >> >> I repeat: it’s experience with dt 3.2.1 for Windows. I am not aware on how >> it behaves on Linux. >> >> >> >> >> >> Marc >> >> >> >> >> >> Van: GianLuca Sarto <mailto:[email protected]> >> Verzonden: zondag 15 november 2020 21:30 >> Aan: [email protected] >> <mailto:[email protected]> >> Onderwerp: Re: [darktable-user] Ubuntu 20.04, OpenCL, DT3.2.1, Radeon HD5400 >> >> >> >> thanks, Šarūnas, >> >> >> >> I have two Darktable systems, based on Lenovo TS140, one with AMD, the >> >> other with Nvidia Quadro 400. >> >> Neither of the two manage OpenCL.. >> >> >> >> 0.039390 [opencl_init] found opencl runtime library 'libOpenCL' >> >> 0.039412 [opencl_init] opencl library 'libOpenCL' found on your system >> >> and loaded >> >> 0.042560 [opencl_init] found 1 platform >> >> 0.042582 [opencl_init] found 1 device >> >> 0.042727 [opencl_init] device 0 `Quadro 400' has sm_20 support. >> >> 0.042778 [opencl_init] discarding device 0 `Quadro 400' due to >> >> insufficient global memory (511MB). >> >> 0.042784 [opencl_init] no suitable devices found. >> >> 0.042788 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. >> >> >> >> I would like to upgrade one of the two systems to a 4K display, so was >> >> already decided to purchase a new video card. >> >> >> >> Is there a tested solution that works out of the box, or a list of DT >> >> OpenCL compliant cards for Linux? >> >> >> >> >> >> >> >>> On 15/11/20 15:34, Šarūnas wrote: >>> >>> On 11/14/20 3:41 PM, GianLuca Sarto wrote: >> >>>> Hello All, >> >> >>>> DT 3.2.1 here, running on Ubuntu 20.04, Radeon HD5400. >> >> >>>> OpenCL should be working, however DT complains "could not get platforms" >> >>>> (see below). >> >>> Support for Radeon HD5xxx may have ended with fglrx (Ubuntu 16.04?). >> >> >>> You may check what is currently supported, >> >>> by proprietary AMDGPU-PRO: >> >>> https://www.amd.com/en/support >> >> >>> by open source ROCm: >> >>> https://github.com/RadeonOpenCompute/ROCm#Hardware-and-Software-Support >> >> >> >> >> ____________________________________________________________________________ >> >> darktable user mailing list >> >> to unsubscribe send a mail to [email protected] >> <mailto:[email protected]> >> >> >> >> >> >> >> ____________________________________________________________________________ >> darktable user mailing list to unsubscribe send a mail to >> [email protected] >> <mailto:[email protected]> >> >> >> >> >> ____________________________________________________________________________ >> darktable user mailing list to unsubscribe send a mail to >> [email protected] >> <mailto:[email protected]> >> >> >> ____________________________________________________________________________ >> darktable user mailing list >> to unsubscribe send a mail to [email protected] > > > your parameters may be off for opencl_synch_cache, I have: > opencl_synch_cache=active module > > > -- > (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri > http://en.opensuse.org openSUSE Community Member facebook/ptilopteri > Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected] > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
