Just tried this while resuming an upload that disconnected last night, here’s the output: Skipped chunk 8693aeb0f80540021d880c9e2a995ed276f9a666fe5cdfe5c47785d107e25edc in cache I feel like there’s an obvious mistake I’m making or a switch somewhere I need to toggle, any ideas what could be causing the speed issues? I recently upgraded from 2.6.2 which had the same issue. I am running Windows Server 2019 with the latest updates installed, with duplicacy command line 2.7.1. A speedtest on the same computer returns a stable 35 Megabits upload speed. This resulted in the initial upload taking a month or two to complete. The speed I had at the start of the upload was maxing out the connection, but now I am getting is about 2 megabits per second towards the end of the upload, and stays that slow on subsequent runs even now when the initial upload has completed. I noticed high memory usage, then I read somewhere about a month ago that the ‘DUPLICACY_ATTRIBUTE_THRESHOLD’ environment variable being set to ‘1’ helps, so I’ve done this and now only 8/16GB of RAM is used total on the machine (previously Duplicacy would use all available RAM) but see no improvement. I am uploading to a GSuite account and using the following command: duplicacy backup -stats -vss -threads 8 I love duplicacy but sadly have one issue, my duplicacy upload speed when using it gets worse as the upload progresses, or more accurately, the more files already backed up as this persists in further runs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |