Am 22.12.19 um 19:32 schrieb Jochen Keil:
However, both denoise module, which used to run perfectly on the GPU,
now fall back to CPU and add around 14s each!
According to the log there's a tiling issue, but I don't understand why.
It's still the same 6GB GPU that used to work with 2.6.x.
You might need to adjust parameter opencl_memory_headroom in
darktablerc. In your case it's set at its default 300MB. The parameter
tells darktable how much of the total VRAM it should assume to be
reserved by other processes. darktable then takes all the rest. Now, if
this parameter it set too low darktable will fail in GPU memory allocations.
You should have on your system the nvidia-smi tool. It will tell you how
much of the memory is currently used. This would be a first starting
point for opencl_memory_headroom.
I recently have learnt that on a typical KDE system one of the
components (plasmashell, krunner, ...) is notorious for leaking GPU
memory. The longer the system runs the less VRAM is free. You should be
able to see this if you follow up on nvidia-smi for a longer time.
It is said that calling from time to time this script would free GPU
memory again:
#!/bin/bash
kquitapp5 plasmashell
kstart5 plasmashell &
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
