In my use of rclone mount, I often rescan one entire directory tree.
Given this access pattern, a find across the whole directory tree via the rclone mount takes about 1 minute 35 seconds. However, rclone --fast-list ls on the same directory takes about 5 seconds.
When a directory is listed on an rclone mount (e.g. ls), would it be an interesting idea for rclone to trigger a recursive directory listing to warm the directory cache? I know I'm going to be adding more directories and files into the structure. Curious if you've considered that and what you think of adding that as an option.
Huh - the 1 min 35 second find is on a Google Drive backend with a --poll-interval of 60s. (Should I retest to make sure my memory is right about that?) Seems to me find (on the rclone mount) and rclone --fast-list ls should be about the same speed if the cache is warm, and indeed the second recursive find is in the 1-2 second range.
It sounds like a good solution for me is to keep the cache warm directly with either vfs/refresh or find myself, so I'm happy with this answer, but wanted to express that confusion.