the cache folders seem very excessive so what is stored in here causing such bloat and how can we reduce the requirements

Hi Adam.  What's the overall vault size?

Hi Craig
its 1.4TB within the vault folder structure in Windows.

Hmm.

I don't have any specific guidance here - I don't think I've configured the shared cache in production use - but note that the shared cache does contain everything which users may have marked for offline or has otherwise been needed by the client recently.  50GB is a lot, naturally, but it's about 3.5% of the total vault size by sounds of it.

Thanks Craig, 50GB does seem a lot but 3.5% is probably more the key figure to look at.  Does this cache self clear itself down once users don't access files for a specific period of time or if the user unmarks them for offline access?

Thanks Craig, 50GB does seem a lot but 3.5% is probably more the key figure to look at.  Does this cache self clear itself down once users don't access files for a specific period of time or if the user unmarks them for offline access?

I'm going to be a little cautious here because, as I said, I don't think I've configured the shared cache in production use.

As a general point you can control cache settings via the desktop settings app, and there are ways to clear the cache down as well, but I am not 100% sure what the implication of the shared cache is.

I hate doing tagging colleagues, but maybe Joonas Linkola has some visibility on this?  If not then perhaps I can raise the question internally and see what feedback I can get.

Unfortunately I have very limited experience with shared caches. M-Files Support might be able to comment on whether the cache size / ratio to the vault size seems normal and if there are any relevant configuration options to control this.

Thanks Joonas and Craig, I appreciate your time.  I'll raise the question via support as well, I just wanted to gauge what other peoples experience with this was to understand if we've misconfigured something.