Danny Sep 6 1:36PM 2017 CLI
If I run backup with no -limit-rate argument, my backup runs at a very steady 14-15 Mbps (I can see this in the dashboard for my NAS). If I run it with -limit-rate 1024, it runs ... well ... around 1 kbps. I guess it seems self-evident why this is, obviously it's interpreting the argument to -limit-rate as bits per second. But the documentation says this is in kilobytes per second.
-limit-rate the maximum upload rate (in kilobytes/sec)
So my upload is going ~8000 times slower than it should be.
I guess this is a documentation bug.
Danny Sep 6 2:46PM 2017
I'm confused about what's happening here. The graph was hard to read with the upload rate so low so I might have gotten the number wrong. It's definitely not bits per second because setting it to ~8,000,000 is the same as uncapped.
I'm going to give up on using Duplicacy's rate limiting and use traffic shaping instead.
gchen Sep 6 8:56PM 2017
I'm pretty sure this is not a documentation bug. Are you using the SFTP backend? Could be a bug there.
Danny Sep 6 9:27PM 2017
Bug is in my own brain. It's definitely using 14-15 Mbps uncapped. But I must have been misinterpreting the dashboard after I capped it. In any case traffic shaping is easy to use and lets me adjust the rate on the fly which is a plus for me. Sorry for the noise.