Single filesystem + local repo versus --no-cache

$ restic version
restic 0.17.0 compiled with go1.22.5 on linux/arm64

I must be missing something obvious here, but with the recent questions on this forum about the local cache, I wonder if it is preferable to use --no-cache when applicable if I’m working with a local repository that shares the filesystem with the cache folder.

Are there any benefits of using the local cache anyway in this situation?

Thank you.

You’re absolutely right. If the cache is on the same disk as your repo, it has no benefit. The whole idea of caching is to keep stuff close when you’re dealing with remote repos, to cope with latency etc…

Do use --no-cache flag and you should actually expect things to go little faster (with no unneeded copying between repo and cache on the same disk).

1 Like