duplicity-talk
[Top][All Lists]
Advanced

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

Re: [Duplicity-talk] HubiC Backend: Multi Threaded uploads


From: Tiernan OToole
Subject: Re: [Duplicity-talk] HubiC Backend: Multi Threaded uploads
Date: Wed, 29 Jul 2015 13:17:28 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yea, noticed that GPG is only using 1 of the processors in the
machine, as is duplicity... any plans to make that multi threaded?

- --Tiernan

On 28/07/2015 14:02, address@hidden wrote:
> afair --asynchronous-upload does only what it says. uploading while
> already building the next volume. normally duplicity would wait
> with volume creation for the upload to be finished.
> 
> here is the manpage descr. " --asynchronous-upload (EXPERIMENTAL)
> Perform file uploads asynchronously in the background, with respect
> to volume creation. This means that duplicity can upload a volume
> while, at the same time, preparing the next volume for upload. The
> intended end-result is a faster backup, because the local CPU and
> your bandwidth can be more consistently utilized. Use of this
> option implies additional need for disk space in the temporary
> storage location; rather than needing to store only one volume at a
> time, enough storage space is required to store two volumes. "
> 
> ..ede/duply.net
> 
> On 28.07.2015 14:55, Tiernan OToole wrote:
>> Manual RSync might be the way to go... mind you, looking at the 
>> script, i already have the --asynchronous-upload option turned
>> on... and it makes no difference... Will try the RSync option...
>> Not sure if Hubic supports RSync, but i do have a server in
>> closer to HubiC that has a faster connection... maybe uploading
>> to there and from there to HubiC...
>> 
>> --Tiernan
>> 
>> On 28/07/2015 13:41, Kenneth Loafman wrote:
>>> Nice connection.
>> 
>>> At this point duplicity does not have the capability to handle
>>> this kind of configuration.  You could handle it by backing up
>>> locally and doing the rsync manually (HubiC supports rsync?).
>>> As a second option you could use --asynchronous-upload to get
>>> two connections going which should alternate between the two if
>>> load balanced.
>> 
>>> ...Ken
>> 
>> 
>>> On Tue, Jul 28, 2015 at 5:29 AM, Tiernan OToole 
>>> <address@hidden <mailto:address@hidden>> 
>>> wrote:
>> 
>>> Morning all.
>> 
>>> I am using Duplicity and HubiC to backup some machines and
>>> noticed that when uploading, its only using 1 of my internet
>>> connections (24mb/s up). I have 2 pipes at the same speed, and
>>> was wondering how (if possible) i can get Duplicity to upload
>>> multiple files to the HubiC backend at the same time?
>> 
>>> The connection is load balanced and i ran some tests and can
>>> get a full 48mb/s up if i use multiple rsync connections...
>>> (rsync with parallel).
>> 
>>> Any ideas?
>> 
>>> Thanks.
>> 
>>> --Tiernan
>> 
>>> _______________________________________________ Duplicity-talk 
>>> mailing list address@hidden 
>>> <mailto:address@hidden> 
>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>> 
>> 
>> 
>> 
>>> _______________________________________________ Duplicity-talk 
>>> mailing list address@hidden 
>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>> 
>> 
>> _______________________________________________ Duplicity-talk
>> mailing list address@hidden 
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVuMRYAAoJECWDUKjOk5r1W5cP/R8QufvRyQDdujh99zDHk/Fd
gBeeIuU6DxQSb6J/srEUPYH0O7R1uqNTedfmXBkCfDkZnviB+GWqPhKr3zWbI6Y6
uz+UXTTA3ZgrKGNQOXSzAspGZIAwPMksuDxP4dUznnTa7fLAtqBQl9vnqtb5c4bL
WYe+hWbYMp4PoafgvQpukR3NI74NmlLo9q1xYpNovGO/+pxKIY5jdWdO2Z/8BiqU
J/wuHV4vbqhNHom7CC5pZph8Tsu7nuI5sigVbQDI6YgqZAovFjm0chu0sTmw/pxP
f4vUi9AIykav32N/EVJUBKSYyjvGYdddq2HtOcSbe+Vv1MU4OYtFQ6G6z59J7pLc
/jupnS5w8Y7yVaMTs/6huz9aaKAp2/TFPCbuInfbp2fqVH2qTIomvU6dbnLVvdiI
UvwidH+muQ3GkikkIKO2Ik75AItbDS7HehF6DZgQJsWNa7Kpykedld1znl9t8vYN
qt+S9ERBpVkr1onKVsI+NhjWczpYqdW0YZ55QwUobhMeFSniNYrIx9CNTLuQ571w
PpSYI+yO1TNRf6gW/TgWHkwVv1xqX+2lWqNfJJf67jRKfSzWwDCZwTa91gdxHYXK
bcnbzTR/jfJ9Ver19S5wI11X0w2csBE9vOZdG4g+09C4ElGb737PQ/JK5Zt9scT5
TWIVM2WGLoZrsP1xQGud
=RLTs
-----END PGP SIGNATURE-----



reply via email to

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