Question #676995 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/676995
edso proposed the following answer: and it's not only the backend infrastructure. currently backup file creation (volumes, manifest ...) is also running in the same thread, meaning a volume is created and uploaded and only after that the next is created etc.. exception being the '--asynchronous-upload' where the next volume is prepared during the upload of the previous volume already, but only during upload and limited to one. to conclude, duplicity currently lacks a threading architecture that utilizes multiple cores or optimizes bandwidth. ..ede/duply.net -- You received this question notification because your team duplicity-team is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
