Use duplicity's --asynchronous-upload option

[Nick Welch]

Looking at my system monitor, I notice that while Deja Dup is backing up, it cycles between using lots of CPU and no network, to using lots of network and little CPU. It seems that it's not taking advantage of duplicity's --asynchronous-upload option, which will more effectively utilize the CPU and the network bandwidth simultaneously, resulting in a faster backup. I've used it on the command line and it's worked great for me, although the man page for Jaunty's 0.5.09 (edit: as well as your PPA's 0.5.16) version still warns that it's experimental.

[Michael Terry (mterry)]

Agreed, but I believe there were issues with enabling when I experimented with it. Not that it failed in any way, but the messages output by duplicity got harder to put together in some manner. Can't remember now. I'll have to look back into it.

(Thanks for all these great bug reports!)

[someone1 (prateek)]

I still see this kind of behavior, is there any work being done towards making this more "parallel"?

[someone1 (prateek)]

Definitely did NOT mean to nominate this....

[Fjodor (sune-molgaard)]

Duplicity's man page still says "EXPERIMENTAL", but might I suggest a preference, possibly only exposed to dconf-editor, to enable this, but keep it disabled by default?

As far as I can see, it's only a matter of registering the setting in dconf, check for it when the duplicity command is generated, and then, if set in dconf, add --asynchronous-upload to the command.

All in all, the biggest (small, I assume) challenge is setting and checking in dconf ;-)

[Fjodor (sune-molgaard)]

https://bugs.launchpad.net/deja-dup/+bug/1556089 could also be of relevance...