No, I believe it’s throttled per connection. I’m in Australia and have been using CloudBerry Backup until very recently. On one thread I would get between 1.8 and 3.2 Mbits. When I set up 10+ threads I could easily max out at 40Mbits.
With Duplicati I see the same ‘one connection’ speed. If parallel uploads can be implemented (at least for B2) I’ll be moving everything over to Duplicati!
2 Likes
I have the same issue with Backblaze.
There is a bounty for this over at GitHub, however I don’t know that it’s actively being worked on yet:
opened 07:43AM - 18 Oct 16 UTC
closed 07:41AM - 19 Mar 19 UTC
enhancement
bounty
Some of the cloud backends (e.g. Dropbox) seem bandwidth limited by the cloud pr… ovider for individual connections (upload/download). One way to achieve higher throughput would be to upload backup volumes in parallel. Obviously this only works if there is more than 1 backup volume to be uploaded.
The same approach would also be possible for achieving higher throughput on downloads.
However, an important implication for the backend implementations is that they should be **thread-safe** , i.e. calling PUT should be possible in parallel. Perhaps, an additional interface could be defined, IThreadSafeBackend or something, that IBackends can implement for indicating that they support parallel upload/download operations.
##
<bountysource-plugin>
---
There is a **[$50 open bounty](https://www.bountysource.com/issues/38460805-support-parallel-uploads-for-a-backend?utm_campaign=plugin&utm_content=tracker%2F4870652&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F4870652&utm_medium=issues&utm_source=github).
</bountysource-plugin>
1 Like
Thanks.
1 Like
