The problem is not in the software itself, it is lovely. When used on different seedboxes, the following problem almost always arises. Upload speed to gdrive goes under 10-15mb, sometimes lover than 5mb. I must say right away that the matter is not in the rclone settings, the seedbox traffic limit is not exceeded, google account limit is also normal. It can be assumed that the channel is overused by other users, or the bottleneck to google servers. But I did an experiment, downloaded the contents of the seedbox via ftp and other protocols using the appengine instance directly on the google network. And even through ftp, I easily got 50mbs .. For several reasons, it’s more profitable for me to use shared seedboxes, I ask you not to post recommendations for changing the seedbox / VPS)) The root cause is more interesting than the solution even.
What is the problem you are having with rclone?
seedbox bandwith
What is your rclone version (output from rclone version)
from old stable to fresh betas
Which OS you are using and how many bits (eg Windows 7, 64 bit)
ubuntu 18, debian 9, etc
Which cloud storage system are you using? (eg Google Drive)
Google Drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone copy/move
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
I want to experiment, raise several vpn interfaces of different providers on seedbox. Something tells me that it will give a full band for uploading. I would be grateful if you prompt the command for ubuntu / debian to raise the openvpn / wireguard interface without automatically routing all traffic. And then with my experiments I already dropped my box several times)).
I find that for uploading with rclone --drive-chunk-size makes the biggest difference when it comes to speed. This is especially true if you upload files individually. Use as high a number as your RAM allows. For example, if I upload a single 50GB file with --drive-chunk-size 128M, it will peak around 30MB/s. If I use --drive-chunk-size 1024M or even higher, the speed will go up to max, in my case a capped 95MB/s. This parameter has less of an impact if you upload many files at the same time.
Same here, but I use RcloneBrowser to upload, with --drive-chunk-size set to 128M by default. This works well when I upload an average of 120 files per session. If it's fewer files, I increase the chunk size, if it's more, I decrease. My dedicated server has 32GB of RAM and gig up/down. RcloneBrowser set to --transfers 999 --checkers 8
