This article will guide you on steps to troubleshoot Redis #latency problems.
#Amazon #ElastiCache allows you to seamlessly set up, run, and scale popular open-source compatible in-memory data stores in the cloud.
Build data-intensive apps or boost the performance of your existing databases by retrieving data from high throughput and low latency in-memory data stores.
#Redis #performance monitoring metrics:
1. Used Memory
"memory_used" gives the total amount of memory in bytes that is used by the Redis server. If it exceeds physical memory, system will start swapping causing severe performance degradation.
2. Peak used memory
"memory_used_peak" metric calculates and displays the highest amount of memory in bytes consumed by the Redis server.
3. Used CPU system
The metric "cpu_used_sys" gets the total amount of system CPU consumed by the Redis server. High CPU usage is not bad as long as it doesn't exceed CPU limit.
4. Used CPU user
The metric "cpu_used_user" records the total amount of user CPU consumed by the Redis server.
5. Used CPU user children
The metric "cpu_used_user_children" records the total amount of user CPU consumed by other background processes.
6. Used CPU system children
Get the total amount of system #CPU consumed by background processes with the metric "cpu_used_sys_children".
7. Rejected connections
Use the metric "total_conn_rec" and get the total number of connections accepted by the Redis server.
8. Connected clients
Get the total number of slave connections made to the Redis server with the metric "conn_slaves".