On Monday, 29 October 2018 22:55:44 CET Aurélien Pierre wrote:
> Hallo Heiko !
>
> Very pleased to hear that (not the bug part, though).
>
> Did you try with smaller pictures ? Usually, darktable falls back to CPU
> when there is not enough ressource available on the GPU.
>
> You can try :
>
> 1. the command *nvidia-smi* to see how the GPU RAM is used (if there is
> not enough vRAM available, you will see an OpenCL error code -4).
> 2. setting opencl_async_pixelpipe=true in darktablerc
> 3. setting opencl_mandatory_timeout > 200 in darktablerc
>
> Also, I have discovered this week that Gnome 3.28.2 with Xorg has
> serious memory leaks issues and can affect OpenCL performance. After
> several hours of uptime, Xorg consumes up to 1GB RAM/vRAM on Ubuntu
> 18.04, so OpenCL has not enough space.
Normally you need to select "very fast gpu" that darktable runs more stuff via
OpenCL and this bright a huge boost when processing.
However this doesn't work for me right now. I've started to use the ROCm open
soruce stuff from AMD but it doesn't have image support yet.
Andreas
--
Andreas Schneider a...@cryptomilk.org
GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
