Cache Backend being removed

I read in one of the Github issues that "Cache" is going away at some point. I was hoping you could elaborate on what that means and why so we can plan appropriately.


Does this help?

May I ask why you use the cache today?

I want to have a more integrated replacement. I expect we could do backwards compatibility also so the cache config was applied to the new subsystem.

1 Like

Makes sense.

How are you handling write reliability (offline uploads), persistent meta caching, and some of the other things Cache does that Vfs doesn't (that I'm aware of)?

or am I misunderstanding that VFS will replace Cache?

(maybe your rebuilding the Cache backend and bringing it in house?)


We use Cache for many things and hundreds of mounts. We spent a great deal of time experimenting and VFS never cut it (especially with Crypt in the mix).

Some of the things we rely on (albeit wish were better) are offline uploads, separate index and chunk destinations, persistent meta storage, hot block caching (sub file reads).

Take a look at:

For a rough summary, it's being integrated into the base VFS mount so things in cache are being moved into the 'standard'. If you have very specific use cases, feedback would be welcome along with testing!

1 Like

Just went through the post and quickly browsed through the vfs branch. The branch looks really promising. The new VFS functionality doesn't appear to be missing any features that Cache brings to the table. Did I miss something?

1 Like

I don't think so.

The only thing missing per se, Plex integration, which had a great idea, but not really needed.

Other than that, I think the future is looking bright!

1 Like

We never enabled Plex integration as it caused other issues where a mount might be used for other things beyond media.

@tcf909 Care to elaborate a bit on your use of rclone? Sounds like a interesting way to use it.

The VFS cache will help with some of that - offline uploads should work. The metadata is kept as small files on the disk so I don't think will be a problem unlike the cache db. It will do sub file reads too.

One thing it doesn't do yet is cache metadata persistently (other than for files it has cached). I'm planning on doing this eventually but one thing at a time!

1 Like

Running beta 044 and it is smooth as butter. :+1:

Any bugs stopping it from merging with mainline beta?



1 Like

Hi Anim. Yes - I meant to post in that thread... bounced tabs by accident.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.