[response-cache-redis] - Configurable TTL for tags

[klausXR]

Hello, I got this plugin to work in my application, however, I noticed that there is a configurable TTL for the cache key of the query, but the tags have a TTL of -1.

How should I solve the problem of memory overflowing when there is a lot of data, what eviction policy should I use?

• allkeys-lru will purge the tags before the queries, since the tags are seldom queried
• volatile-lru wont purge the tags, because they have -1 TTL
• volatile-ttl also wont work due to the -1 TTL

How should I approach this? I think the volatile-ttl is a good one if query has 2h TTL and the tags have 3h, that way they have less of a chance of getting evicted, however, the lru part doesn't work with that policy

According to the docs here, the volatile-ttl should be a good candidate, because it takes into account the usage frequency, so a configurable ttl for the types may be a good feature to have.