So my general mantra with this stuff is keep it simple. I try to use the defaults wherever it makes sense to keep them.
rc - you are correct as that’s only used for remote control commands. If you don’t plan to use it, you can remove this option
dir-cache-time and vfs-cache-max-age-duration are two different things. dir-cache-time is how long the directory and file system will stay unless a polling interval invalidates them. I personally keep this as big as possible as the bigger the better imo. 72 hours or something along those lines helps reduce API hits that aren’t needed as nothing changed so why repoll.
all the vfs-cache commands relate back to the vfs-cache-mode that you are using. So if you are using writes, any write stays in cache (local disk) until the age expires.
drive-chunk-size is only for uploads and works with using vfs-cache-mode-writes and sends the uploads broken up in chunks. Your upload speed really doesn’t matter as it just uploads a 512M chunk over time and it takes however long your upload is. There have been a few tests on this and 32M or 64M seems to be a sweet spot for it.
poll-interval is how often rclone polls Google Drive for changes. 1 minute is the default and really should be just left alone.
All the vfs-cache options are written up here:
as the vfs-cache-poll-interval only impacts what is in the actual vfs-cache.
fast-list does nothing on a mount so can be removed.
Your buffer-size at 1G means every file opened consumes 1GB of memory so be sure you have enough memory to handle whatever your max load is. Again, I don’t see much value in this personally so I keep this at the default.
My mount is simple:
/usr/bin/rclone mount gcrypt: /GD --allow-other --dir-cache-time 96h --drive-chunk-size 32M --log-level INFO --log-file /opt/rclone/logs/rclone.log --timeout 1h --umask 002 --rc
We talked about the cache time and I use 96 hours.
Timeout is for resuming playback in plex.
umask is to set permissions
I use remote control so I keep that.