Caching

For general purpose workloads, the caching policy is reccommended.

The all cache policy is the opposite of the cache policy. All blocks are kept in memory until their retention period is over. This policy can be useful for read-heavy workloads with small datasets, but is obviously limited by the amount of memory on the host machine. Also keep in mind that this cache policy may have unintended side-effects on write throughput as keeping every block in memory creates a lot of work for the Golang garbage collector.

Data eviction from memory is triggered by the “ticking” process described in the background processes section