Add Transfers field to Cloud Sync in legacy UI
As outlined https://rclone.org/b2/, otherwise large cloudsync tasks are slow.
Backblaze recommends that you do lots of transfers simultaneously for maximum speed. In tests from my SSD equipped laptop the optimum setting is about --transfers 32 though higher numbers may be used for a slight speed improvement. The optimum number for you may vary depending on your hardware, how big the files are, how much you want to load your computer, etc. The default of --transfers 4 is definitely too low for Backblaze B2 though.
Note that uploading big files (bigger than 200 MB by default) will use a 96 MB RAM buffer by default. There can be at most --transfers of these in use at any moment, so this sets the upper limit on the memory used.
#4 Updated by Vladimir Vinogradenko about 2 years ago
- Status changed from Unscreened to Screened
--transfers option as a cloud sync option. Some people might want slow background sync that does not affect their NAS and network performance and some may afford pushing 10 GBits to S3 with CPU being used at 199.9%
Low risk, it's just another option with default value set to what's it already is
Create a cloud sync task, set "The number of file transfers to run in parallel" option to some value e.g. 5. Set it to sync relatively large amount of data so you can catch it in
ps ax | grep rclone while it's running. Run it. Command line should contain
--transfers=5 among all other options and cloud sync task should succeed.