Matthias Bodenbinder writes:
> Am 06.03.2017 um 20:45 schrieb David Bremner:
> Now I got your point. I downloaded 2.2.3-2 and tested it. The speed
> improvement is minimal: 19,6 s for the whole pixel pipeline vs. 21,9 s
> for version 2.2.3-1 and compared to 14 s for self-compiled.
I managed to
Am 06.03.2017 um 20:45 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>> Am 06.03.2017 um 13:07 schrieb David Bremner:
>>> Matthias Bodenbinder writes:
>>>
>>> Is that 32% difference with 2.2.3-1 or with 2.2.3-2?
>>>
>>> d
>>>
>>
>> Yes, this is the diff between DT 2.2.3 self-compiled v
Matthias Bodenbinder writes:
> Am 06.03.2017 um 13:07 schrieb David Bremner:
>> Matthias Bodenbinder writes:
>>
>> Is that 32% difference with 2.2.3-1 or with 2.2.3-2?
>>
>> d
>>
>
> Yes, this is the diff between DT 2.2.3 self-compiled vs. debian
> experimental. But the diff is basically the
Am 06.03.2017 um 13:07 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>>
>> I am wondering if it has to do with the fact that I am using the latest Kaby
>> Lake CPU i7-7700k?
>>
>> The Equalizer module in my case improves from 6,9 s to 3,0 s and non-local
>> means noise reduction impr
Matthias Bodenbinder writes:
>
> I am wondering if it has to do with the fact that I am using the latest Kaby
> Lake CPU i7-7700k?
>
> The Equalizer module in my case improves from 6,9 s to 3,0 s and non-local
> means noise reduction improves from 10,3 s to 8,7 s.
>
> They both sum up to 17,2
Am 05.03.2017 um 18:41 schrieb David Bremner:
> I'm not able to reproduce the large difference between the debian
> package and compiling with
>
> ./build.sh --disable-gnome-keyring --build-type Release
>
> On my machine (an older i7), I get an average of 40s to export with
> 2.2.3-2 (compiled w
Matthias Bodenbinder writes:
> Am 28.02.2017 um 13:25 schrieb David Bremner:
>> Matthias Bodenbinder writes:
> 1) download this RAW file: http://www.mirada.ch/bench.SRW
> 2) the xmp file for my test is attached to this email (bench.SRW.xmp)
> 3) put both files in the same directory
> 4) disable
Am 28.02.2017 um 13:25 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>>
>> I can provide DT 2 and DT 3 as deb files (approx. 9 MB each).
>>
>
> That's not needed (or helpful). But did you some place provide the
> actual benchmark you are running, including the data?
>
> I don't use th
Matthias Bodenbinder writes:
>
> I can provide DT 2 and DT 3 as deb files (approx. 9 MB each).
>
That's not needed (or helpful). But did you some place provide the
actual benchmark you are running, including the data?
I don't use the equalizer, so I suspect my images won't show such a
dramatic
Hi,
I did the comparison also with DT 2.2.3-1 from experimental and a self-compiled
binary. The result is the same:
self-compiled (opencl deactivated):
[dev_process_export] pixel pipeline processing took 14,006 secs (108,940 CPU)
binary from experimental (opencl deactivated):
[dev_process_expor
Am 20.02.2017 um 00:36 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>> And by the way, this are the commands I use to compile DT:
>>
>> ./build.sh --disable-gnome-keyring --prefix /home/software/darktable
>> --build-type Release
>> cd build
>> echo "darktable 2.2.1" > description-pak
matth...@bodenbinder.de writes:
>
> Hi,
>
> I do not understand your point. My checkinstall is working fine. It is
> just that my binaries are a lot faster than the debian testing binaries.
>
> Matthias
I was suggesting that you compile with the same cmake options that the debian
package uses. T
On Mon, Feb 20, 2017 at 10:08 AM, wrote:
> Am 2017-02-20 0:36, schrieb David Bremner:
>>
>> Matthias Bodenbinder writes:
>>
>>> And by the way, this are the commands I use to compile DT:
>>>
>>> ./build.sh --disable-gnome-keyring --prefix /home/software/darktable
>>> --build-type Release
>>> cd
Am 2017-02-20 0:36, schrieb David Bremner:
Matthias Bodenbinder writes:
And by the way, this are the commands I use to compile DT:
./build.sh --disable-gnome-keyring --prefix /home/software/darktable
--build-type Release
cd build
echo "darktable 2.2.1" > description-pak
checkinstall --defau
Matthias Bodenbinder writes:
> And by the way, this are the commands I use to compile DT:
>
> ./build.sh --disable-gnome-keyring --prefix /home/software/darktable
> --build-type Release
> cd build
> echo "darktable 2.2.1" > description-pak
> checkinstall --default --install=no --pkgname=darktabl
And by the way, this are the commands I use to compile DT:
./build.sh --disable-gnome-keyring --prefix /home/software/darktable
--build-type Release
cd build
echo "darktable 2.2.1" > description-pak
checkinstall --default --install=no --pkgname=darktable-mbo
--pkgversion=$version --docdir=$INST/
Hello Roman,
attached are the 2 log files you where asking for.
Matthias
Am 17.02.2017 um 08:25 schrieb Roman Lebedev:
> On Fri, Feb 17, 2017 at 10:03 AM, Matthias Bodenbinder
> wrote:
>> Package: darktable
>> Version: 2.2.1-2
>> Severity: normal
>>
>> The darktable binary from debian testing
On Fri, Feb 17, 2017 at 10:03 AM, Matthias Bodenbinder
wrote:
> Package: darktable
> Version: 2.2.1-2
> Severity: normal
>
> The darktable binary from debian testing is very slow compared to a
> self-compiled version.
> 1) apt-get install darktable
> The darktable-cli benchmark I am using takes 2
Package: darktable
Version: 2.2.1-2
Severity: normal
The darktable binary from debian testing is very slow compared to a
self-compiled version.
1) apt-get install darktable
The darktable-cli benchmark I am using takes 22 seconds to complete
2) apt-get source darktable && compile myself
The dark
19 matches
Mail list logo
