Closed giangcoi48k closed 4 years ago
Nope that's how CM works today. The meta data is needed to allow timeouts per cache key and support sliding expiration and all those things. It is a bit of an overhead but I think it's a good trade-off.
@giangcoi48k I'd gander that if the overhead is too much, you're going to be needing to have fine-grained control over your cache implementation anyway (custom data types, eviction mechanisms etc). But I would personally try it and only decide it's too much if performance tests say so.
I am intending to use CacheManager for my netcore project. I configured the following
It work well. But when I looked into redis, there are redundant keys in hash, like timeout, version, defaultExpiration,... For example, I puted one key test like
_cacheManager.Put("Test", "Test Value");
, the value I got: I think it's a waste of memory if there are lots of keys with small value. So, is there any way only store value and key, and ignore the redundant keys? Sorry for my bad English