Client side caching eviction policy

[arindamnayak]

I am looking forward to use this library in one of the product. This library provides server assisted client side caching which means it can cache the look up in local memory. I am more interested how the cache eviction happens at local memory. I know there is a setting to control the local cache size ( default value is 128 MB). So when the memory limit is reached, how the data is removed from the local cache? Is there any policy can be set like LRU or LFU?

[rueian]

Hi @arindamnayak, It is LRU.

[arindamnayak]

It will be helpful if you can point me to the code, where we evict those on condition.

[rueian]

Sure!

rueidis/lru.go

Lines 242 to 253 in 625e68a

	ele = c.list.Front()
	for c.size > c.max && ele != nil {
	if e := ele.Value.(*cacheEntry); e.val.typ != 0 { // do not delete pending entries
	kc := e.kc
	if delete(kc.cache, e.cmd); len(kc.cache) == 0 {
	delete(c.store, kc.key)
	}
	c.list.Remove(ele)
	c.size -= e.size
	}
	ele = ele.Next()
	}

[rueian]

Hi @arindamnayak, did that help you? I would like to hear about what problem you are facing.

[arindamnayak]

Yes, that helped, no problem faced as of now, just exploring the strategy before using it.

[nikhillimaje]

Hi @rueian and @arindamnayak, I'm interested in controlling the local cache size for my application. Could you please share how do we do that? Thanks.

[rueian]

Hi @nikhillimaje, we have the CacheSizeEachConn option for you to control the estimated cache size for each connection.