On 02/11/2018 03:06 PM, Bernhard wrote:
>
>
> Roman Lebedev schrieb am 11.02.2018 um 20:47:
>> On an unrelated note: not everyone speaks ${langname}
>>
>> Roman.
> sorry, but could figure out how to change:
>
>
> Michael Rasmussen schrieb am 11.02.2018 um 16:42:
>> If you do this what do you get?
>> $ wgethttp://www.mirada.ch/bench.SRW
>> $ wgethttp://www.mirada.ch/bench.SRW.xmp
>>
>> $ darktable-cli bench.SRW test.jpg --core --disable-opencl -d perf
>> >>> pixel pipeline processing took 40,388 secs (215,986 CPU)
>>
>> $ darktable-cli bench.SRW test.jpg --core -d perf -d opencl
>> >>> pixel pipeline processing took 8,440 secs (15,970 CPU)
>
> ~ $ darktable-cli bench.SRW test.jpg --core --disable-opencl -d perf
> [...]
> [dev_process_export] pixel pipeline processing took 28,220 secs (105,356
> CPU)
>
> ~ $ darktable-cli bench.SRW test.jpg --core -d perf -d opencl
> [...]
> [dev_process_export] pixel pipeline processing took 7,026 secs (9,684 CPU)
> [export_job] exported to `test_05.jpg'So it looks like using GPU with OpenCL gives a nice speedup from 28s to 7s. When it works. I can't tell, why disin't it wrok in your previoaus attempts, but here some empirical suggestion. 1. Backup you current darktable config (~/.config/darktable/darktablerc) to somwhere safe. 2. Delete it and let darktable create it anew on ext start. 3. See what you get with processing times. If it now uses GPU, check the difference between the new and your old darktablerc (diff darktablerc darktablerc_old). -- Šarūnas Burdulis math.dartmouth.edu/~sarunas
signature.asc
Description: OpenPGP digital signature
