Am 29.10.18 um 22:55 schrieb Aurélien Pierre:
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
This did not help. Finally, I set explicitly
opencl_device_priority=*/!0,*/*/*
which is according to the documentation is the default. Now the GPU is
enabled except for the preview pixelpipe, as also indicated by the log:
0.208921 [opencl_priorities] these are your device priorities:
0.208925 [opencl_priorities] image preview export thumbnail
0.208934 [opencl_priorities] 0 -1 0 0
0.208941 [opencl_priorities] show if opencl use is mandatory for a given
pixelpipe:
0.208945 [opencl_priorities] image preview export thumbnail
0.208953 [opencl_priorities] 0 0 0 0
The default
opencl_device_priority=
, however, yields on my laptop
0.209700 [opencl_priorities] these are your device priorities:
0.209703 [opencl_priorities] image preview export thumbnail
0.209711 [opencl_priorities] -1 -1 -1 -1
0.209716 [opencl_priorities] show if opencl use is mandatory for a given
pixelpipe:
0.209719 [opencl_priorities] image preview export thumbnail
0.209724 [opencl_priorities] 0 0 0 0
I.e., no pixelpipe is processed on the GPU.
Heiko
--
-- Number Crunch Blog @ https://www.numbercrunch.de
-- Cluster Computing @ https://www.clustercomputing.de
-- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
