In your application, performance issues can easily be mistaken for out-of-memory issues with your Redis database when the problem may have to do more with hardware or network latencies between your client application and your backend server. Latency, as understood in the Redis community, is broken down in three ways:
Command latency: This is the amount of time it takes to execute a command. Some commands are fast and operate in O(1) while other commands have O(n) time complexity and are thereby a likely source of this type of latency.
Round-trip latency: The time between when a client issues a command and then receives the response from the Redis server that can be caused by network congestion.
Client-latency: If multiple clients attempt to connect to Redis at the same time, concurrency latency can be introduced as later clients may be waiting in queue for early client processes to complete.
To help debug issues, Redis has a special mode for monitoring command...