Documentation - Full Cache Behavior

[watermark]

The documentation isn't clear as to what occurs when the cache is full. Does it implement some eviction strategy (ie. LRU), or does it just not accept any new data until the max-age is reached on the existing data? I don't think anything needs to necessarily change with the container, but additional documentation on this matter may help others in deciding what cache values are appropriate for them.

[unspec]

The answer to the question is that nginx will automatically evict the coldest data in the cache, once the cache reaches the limits defined as per https://github.com/lancachenet/monolithic#tweaking-cache-sizes

It probably wouldn't hurt to explicitly call that out somewhere in the documentation / FAQ as you suggest.

[renssies]

I would love to see the information as well. I was not aware that the default cache size is set to 1TB. During my (small) LAN party the cache stopped working because the 512GB disk was getting full and Ubuntu disallowed the creation of files.

I've since ordered a 1TB drive but I would like to see more information on recommended hardware specs and the settings for the cache's disk en memory size.

[unspec]

Hi @renssies - the info around changing the cache size to match your disk space is already documented:

https://github.com/lancachenet/monolithic#tweaking-cache-sizes