Two observations:
1) the total time that darktable reports per pixelpipe lies in the range
of 0.15s. That's not particularly fast, given your very undemanding
history stack, but it's also not extremely slow either. What wonders me
is your observation that the time spent in pixelpipe does not sum up to
your wall time with a discrepancy of a factor 10. There might be other
elements eating up performance on your system...
2) you don't report profiling info per OpenCL kernel. This is normally
printed along the other information when running with '-d opencl -d
perf'. Did you happen to set opencl_number_event_handles to zero? You
should set this to a reasonable high value like 25.
Ulrich
Am 03.12.18 um 14:40 schrieb Volker Lenhardt:
Am 03.12.18 um 12:11 schrieb Volker Lenhardt:
Am 02.12.18 um 17:12 schrieb Volker Lenhardt:
There's still the problem of too slow response with shifting a zoomed
in image to have e.g. a quick look at the corners to detect chromatic
aberration. And cropping an image is slow, too. All of this rating is
compared to what I was used to under Linux with less confined equipment.
I made another test using the command+arrow_keys to scroll once around a
zoomed in image. It is a good deal faster than using the trackpad.
I scrolled from the middle to the upper border, then to the left border,
down to the bottom, then to the right and up again and back to the
middle (i.e. once around the outer part of the image). Counted by the
output of "darktable -d perf" it took about 5 (6 CPU) seconds. In real
time I measured 50 seconds.
That's no fun.
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
