Project

General

Profile

Bug #12228

In darkroom mode, most edits could feel twice as snappy

Added by Ric Flomag 10 days ago. Updated about 10 hours ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Darkroom
Target version:
-
Start date:
06/09/2018
Due date:
% Done:

0%

Affected Version:
2.4.4
System:
Ubuntu
bitness:
64-bit
hardware architecture:
amd64/x86

Description

This could be a quite a leap in making user experience snappier.

Steps to reproduce :
1) use common but computationally intensive modules (equalizer, profiled denoise for instance) so that rendering changes (when "Working..." is displayed) has a noticeable delay (about one second, which is typical for 20 Mpix images on my hardware, NVidia 1050).
2) make any incremental edit, for example adjust exposure by rolling the mouse wheel on the histogram.

Observed : the first incremental change (one click of the wheel) is fully rendered, then a 2nd render is done, showing the result of the edit.
Expected : rendering of all incremental changes (every click of the wheel) is immediately interrupted by the next one. So as only the last one is really rendered.

In many cases, the expected behavior results in rendering the edit twice faster.

History

#1 Updated by Christian Kanzian about 10 hours ago

1) use common but computationally intensive modules (equalizer, profiled denoise for instance) so that rendering changes (when "Working..." is displayed) has a noticeable delay (about one second, which is typical for 20 Mpix images on my hardware, NVidia 1050).

Since I use OpenCl this is the case with "cheaper" Nvidia GPUs. I started with a GT640 and mentioned moduls were dam slow. Looking at benchmarks there is a big jump between 1050 and 1060, which is much faster. So I picked a 1060. In between I had a AMD R9 270X, which feld snappier.

I upgraded my nvidia driver from 375.82 to 390.48 as well as the kernel to 4.16. darktable feels much snappier now. So maybe it is a driver issue beside hardware limits as well?

There are a few parameters for OpenCl, which can be adjusted in the darktablerc configuration file: https://www.darktable.org/usermanual/en/darktable_and_opencl_optimization.html Maybe there is some room for tweaks here as well?

Also available in: Atom PDF