A high cache info time works well to make the drive appear more snappy when navigating and also cuts down on a lot of time when syncing since it doesn't have to make a lost of list requests to traverse everything.
That said, be very aware of what the potential downfalls are.
Most importantly, very long info expiry timers should only be considered safe if ALL changes to it happens though this cache point. Otherwise, file info can become out of date and incorrectly displayed. In best case you don't see file changes done outside your cache. At worst files can get corrupted because it assumes a wrong size when it works with them.
I use long cache expiry timers myself, but only after thoroughly understanding them. Even other rclone instances on the same machine must be considered here...
Common pitfalls to be aware of:
- Confusing VFS cache and backend cache parameters. Read up on which apply to which and know that these do not coordinate with eachother. Also consider their order if you use the cache-backend.
- Setting a VFS --dir-cache-time higher than --cache-info-age (this must be avoided). If you have a high --cache-info-age (assuming that you use the cache backend that is) you can leave the VFS timer to default.
- Forgetting that other rclone instances, such as daily syncs, also have to go through the cache to avoid your cache info becoming incorrect.