What is the problem you are having with rclone?
I am using rclone mount to sync media files and it works great but am looking for further optimisations.
My question is around how --buffer-size should be configured relative to --drive-chunk-size:
- If buffer-size is less than drive-chunk-size, will the buffer even be used (as each drive chunk cannot fit into the buffer)?
- Is it beneficial to make the buffer-size at least twice as large as the drive-chunk-size as I have done (see below) so that rclone 'reads ahead' more?
- Does --vfs-read-chunk-size come into play at all or are its effects orthogonal to --buffer-size and --drive-chunk-size?
What is your rclone version (output from
$ rclone version rclone v1.49.3 - os/arch: linux/amd64 - go version: go1.12.9
Which OS you are using and how many bits (eg Windows 7, 64 bit)
$ uname -a Linux core1 4.19.68-coreos #1 SMP Wed Sep 4 02:59:18 -00 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg
rclone copy /tmp remote:tmp)
/opt/bin/rclone mount gcrypt: /mnt/google-drive \ --config=/root/.config/rclone/rclone.conf \ --vfs-read-chunk-size=128M \ --vfs-read-chunk-size-limit=off \ --drive-acknowledge-abuse=true \ --drive-chunk-size=128M \ --buffer-size=256M \ --use-mmap \ --attr-timeout=72h \ --dir-cache-time=72h \ --gid=1000 \ --uid=1000 \ --modify-window=1s \ --stats=0 \ --log-level=INFO \ --allow-other \ --fast-list
And my config
[gdrive] type = drive client_secret = [REDACTED] scope = drive token = [REDACTED] client_id = [REDACTED] root_folder_id = [REDACTED] [gcrypt] type = crypt remote = gdrive: password = [REDACTED] password2 = [REDACTED]