Comment on Redis explainedparentComments−tomnipotent4yThere are workloads that will saturate a redis instance's CPUI might imagine this scenario if you're excessively using smembers and a few other slow ops, but I have yet to see CPU issues outside of bad eval's.require finding old keys to deleteLRU/LFU eviction is not particularly CPU intensive.redis to do memory defragmentation which can be fairly intensiveActive defrag has relatively negligible overhead, and assuming jemalloc even more so.−mnutt4yNothing but lots of small (~100b) pipelined SETs and a small number of GETs here and there. Only 10MB/s but at 100k SETs/sec redis’s CPU core sits at 60-70%. Active defrag can easily send it into a death spiral.
Comments
I might imagine this scenario if you're excessively using smembers and a few other slow ops, but I have yet to see CPU issues outside of bad eval's.
LRU/LFU eviction is not particularly CPU intensive.
Active defrag has relatively negligible overhead, and assuming jemalloc even more so.
Nothing but lots of small (~100b) pipelined SETs and a small number of GETs here and there. Only 10MB/s but at 100k SETs/sec redis’s CPU core sits at 60-70%. Active defrag can easily send it into a death spiral.