Understanding --drive-pacer-burst (Google Drive)

--drive-pacer = 100ms (default)
--drive-pacer-burst = 100 (default)

100 transactions in 0.1 seconds is 1,000 transactions per second

1,000 transactions in per second is 100,000 transactions in 100 seconds.

But no more than 20,000 transactions per 100 seconds is allowed to occure?

I can see this pull request, where it changed from 10,000 (per 100 seconds) by default (which was within the limit): drive: increase pacer to 100ms by default · Issue #2880 · rclone/rclone · GitHub

Am I missing something here? Because it looks like the default settings are non-functional.

Also, how does this interact with --tpslimit? Does none of this matter as long as --tpslimit is 200 or under? Everyone has said to make my limit 10, but it seems it should be 200. Any help on that?

Most of us have been using --drive-pacer-burst 200 --drive-pacer-min-sleep 10ms for quite a while now. As for --tpslimit, why would you need that at all?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.