[penagwin]

At my job we're currently re-building our website in django, and we make heavy use of redis caching.

Our website is definitely not "high traffic" but we get somewhere around 300,000 requests a day, mostly concentrated around business hours (We're a local clothing wholesaler).

I haven't tested it under production loads, but just swapping our redis for keydb (THANKS DOCKER!) I saw no improvement in my artificial load tests.

I didn't expect to see much real improvement for this use case, but I just thought it was worth mentioning that it isn't necessarily faster for all workloads.

[darkr]

We currently do nearly a million requests per minute at peak, on a non clustered redis pair for caching and rate limiting (so at least one read/write per request). This design won’t hold up forever, but we’ve got at least a few years headroom before we need to think about anything more complicated

[wolco]

You would probably need 30,000 million a day but then other parts of your setup would fail. Redis being the bottleneck is an unusual case.

[jdsully]

Sorry we didn’t improve your use case. If you are bottlenecked by Redis I would be curious about your workload.