Has Client-Side Caching been benchmarked under high load?

[a-khakimov]

Hi,

I’m currently experimenting with Client-Side Caching and I’m seeing some performance issues when working with a large number of keys.

In my test setup:

• I create N keys (tested with over 10 million),
• Then use one Lettuce client to GET all of them,
• And another client to DEL these keys.

What I’m noticing is that eviction events (invalidation messages) seem to be processed extremely slowly in this scenario.

My question is:

• Have you performed any load or stress testing of Client-Side Caching?
• Is there any known bottleneck or limitation in how Lettuce processes invalidation messages (e.g., memory pressure, pub/sub event handling, internal queues)?

At this point, I’m still trying to determine whether the bottleneck is in Redis itself or in the client’s handling of invalidation events.

Any insights or shared benchmarks would be appreciated!

Thanks a lot.