Understanding Pacer behavior with Google Drive

hi,
gdrive can be very slow, as we discussed here

based on forum posts, this has become common values to use, so might try
--drive-pacer-min-sleep=10ms --drive-pacer-burst=200

perhaps someone more experienced with gdrive, can offer some tweaks to your command.

by way of comparison, syncing 100,00 files, using wasabi, s3 clone, known for hot storage

2022/03/17 11:13:13 DEBUG : rclone: Version "v1.57.0" starting with parameters ["C:\\data\\rclone\\rclone.exe" "sync" "D:\\files\\100000" "wasabi01:test100000" "--transfers=256" "--checkers=256" "--fast-list" "--progress" "--stats-one-line" "--log-level=DEBUG" "--log-file=C:\\data\\rclone\\rr\\other\\newtest\\100000\\log.txt" "--dry-run"]
2022/03/17 11:13:13 DEBUG : Creating backend with remote "D:\\files\\100000"
2022/03/17 11:13:13 DEBUG : Using config file from "C:\\data\\rclone\\rclone.conf"
2022/03/17 11:13:13 DEBUG : fs cache: renaming cache item "D:\\files\\100000" to be canonical "//?/D:/files/100000"
2022/03/17 11:13:13 DEBUG : Creating backend with remote "wasabi01:test100000"
...
2022/03/17 11:13:49 DEBUG : 7967 go routines active