3 ms·
The idle CPU might very well be due to redis being single threaded. It might be hitting is limits and still show low CPU utilization. Also, you didn't mention
by takeda 7y ago
The idle CPU might very well be due to redis being single threaded. It might be hitting is limits and still show low CPU utilization.
Also, you didn't mention that, but I've seen this happening often, you should never use redis as a primary data store if your data is important.
- cogman10 7y agoYou'd expect a 1/n where n is number of cores available utilization in the case of redis being CPU bound. I guess I don't know how redis deals with the network, but I'd assume that it handles concurrent requests. If not, then I guess that's the case where you'd see less than 1/n cpu utilization and it could still be CPU bound.
- takeda 7y agoRedis handle all request serially, because of that it is much simpler to be correct and doesn't have to worry as much about distributed gotchas. Because redis handles all requests serially you need to be very careful if the redis cluster is shared between different apps. You want to share the cluster among apps with similar usage patterns.