Duplicacy wastes ~50% of available network traffic

[emaileroo_duplicac10]

When I run Duplicacy on my machine (with no other significant programs running) I get the following network traffic pattern:

From that graphic I assume, Duplicacy does open a file, encrypt it and then sends it over the network and again.

I think the network and CPU could be used more effective if that would be separated in two threads, so the network and CPU are steadily used to their full capacity. (or configured limits)

Especially with large backups, this could speedup the whole process quite a bit as most of the time the network is the bottle neck.

Looking forward to get your thoughts on that, or if it maybe is a configuration error on my side.

[leerspace]

Are you already using the -threads option? If not, I think it’s almost exactly what you’re describing. You can configure Duplicacy to use 2 or more threads for uploading.

Reference

Backup command details

The backup command creates a snapshot of the repository and uploads it to the storage. Click here for a list of related forum topics. Quick overview NAME: duplicacy backup - Save a snapshot of the repository to the storage USAGE: duplicacy backup [command options] OPTIONS: -hash detect file differences by hash (rather than size and timestamp) -t <tag> assign a tag to the backup -stats show statistics during and…

[emaileroo_duplicac10]

Oh, wow. Emberassing that I didn’t recognice that option. Works like a charm with more threads