duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] duplicity 0.7 slowness


From: Philip Jocks
Subject: Re: [Duplicity-talk] duplicity 0.7 slowness
Date: Mon, 25 Jul 2016 11:56:34 +0200

Hej Aaron,

> Am 01.07.2016 um 13:41 schrieb Philip Jocks via Duplicity-talk 
> <address@hidden>:
> 
> Hej,
> 
>> Am 30.06.2016 um 16:26 schrieb Aaron <address@hidden>:
>> 
>> Hello Philip,
>> 
>> On 2016-06-30 11:34, Philip Jocks wrote:
>>> The command is
>>> duplicity collection-status --archive-dir /var/.duply-cache --name
>>> duply_zzz --encrypt-key XXXXXXXX --encrypt-key YYYYYYYY --sign-key
>>> XXXXXXXX --verbosity 4 --gpg-options "--pinentry-mode=loopback
>>> --compress-algo=bzip2 --bzip2-compress-level=9" --full-if-older-than
>>> 1W --volsize 200 --ssh-askpass sftp://address@hidden/ccc/ddd
>>> Any options I should remove?
>> 
>> Given your follow-up email, it would be good to rule out SSH as a cause. Can 
>> you please backup to a local folder (e.g. file:///tmp/dup_test) with both 
>> and see if there is still the time difference?
> 
> yeah, that’s what I was thinking, though 0.6 seems to not have made that 
> request. Turns out, there’s the same stuff going on, whatever 0.7 does here:
> 
> 2016-07-01 12:57:44 File 
> duplicity-inc.20160630T150316Z.to.20160630T150715Z.vol171.difftar.gpg is part 
> of known set
> 2016-07-01 12:57:44 File 
> duplicity-inc.20160630T150316Z.to.20160630T150715Z.vol305.difftar.gpg is part 
> of known set
> 2016-07-01 12:57:44 File 
> duplicity-inc.20160630T150316Z.to.20160630T150715Z.vol36.difftar.gpg is part 
> of known set
> [nothing is echoed here, it just does nothing]
> 2016-07-01 12:58:53 File 
> duplicity-inc.20160630T150316Z.to.20160630T150715Z.manifest.gpg is part of 
> known set
> 2016-07-01 12:58:53 File 
> duplicity-inc.20160630T150316Z.to.20160630T150715Z.vol39.difftar.gpg is part 
> of known set
> 2016-07-01 12:58:53 File 
> duplicity-inc.20160630T150316Z.to.20160630T150715Z.vol113.difftar.gpg is part 
> of known set
> 
> The command I run is
> 
> duplicity collection-status --archive-dir '/var/.duply-cache' --name 
> duply_zzz_local --encrypt-key XXXXXXXX --encrypt-key YYYYYYYY --sign-key 
> XXXXXXXX --verbosity '9' --gpg-options '--pinentry-mode=loopback 
> --compress-algo=bzip2 --bzip2-compress-level=9' --full-if-older-than 1W 
> --volsize 200 'file:///path/to/zzz_local'
> 
> time’s output:
> 
> 0.6: 0.41 real         0.28 user         0.03 sys
> 0.7: 71.01 real        37.57 user        23.71 sys
> 
> It’s a single chain, full backup has 3 volumes, one incremental with 1 volume 
> and one incremental with 317 volumes.

have you been able to look into this or maybe even reproduce it?

Cheers,

Philip


reply via email to

[Prev in Thread] Current Thread [Next in Thread]