Detailed explanation of redis info Information A

# Server

Redis_version:2.8.19 # redis version number

Redis_git_sha1:00000000 # git SHA1

Redis_git_dirty:0 # git dirty flag

Redis_build_id:78796c63e58b72dc

Redis_mode:standalone # redis operation mode

Os:Linux 2.6.32-431.el6.x86_64 x86mm 64 # os version number

Arch_bits:64 # 64 bit architecture

Multiplexing_api:epoll # call epoll algorithm

Gcc_version:4.4.7 # gcc version number

Process_id:25899 # Server process PID

Random identifier of run_id:eae356ac1098c13b68f2b00fd7e1c9f93b1c6a2c # Redis (for sentinel and clustering)

Tcp_port:6379 # Port number for Redis snooping

Uptime_in_seconds:6419 # # Redis run time (in s)

Uptime_in_days:0 # # Redis run time (in days)

Hz:10

Lru_clock:10737922 # # self-increasing clock in minutes for LRU management

Config_file:/etc/redis/redis.conf # redis configuration file

# Clients

Connected_clients:1 # # the number of connected clients (excluding clients connected through secondary servers) should also be paid attention to. There will be problems when there is a surge or a significant decline. Even if it doesn't operate,

Client_longest_output_list:0 # # the longest output list among currently connected clients

Client_biggest_input_buf:0 # # the largest client currently connected. Output cache

Blocked_clients:0 # the number of clients waiting for blocking commands (BLPOP, BRPOP, BRPOPLPUSH) needs to be monitored

# Memory

Used_memory:2281560 # # the total amount of memory allocated by the Redis allocator in bytes (byte)

Used_memory_human:2.18M # output the memory consumed by redis in a more friendly format

Used_memory_rss:2699264 # # returns the total amount of memory allocated by Redis (commonly known as resident set size) from an operating system point of view. This value is consistent with the output of top, ps, and other commands, including used_memory and memory fragmentation.

Peak memory consumption of used_memory_peak:22141272 # Redis (in bytes)

Used_memory_peak_human:21.12M # output redis Peak memory usage in a more friendly format

Used_memory_lua:35840 # # amount of memory used by the LUA engine

Mem_fragmentation_ratio:1.18 # = used_memory_rss / used_memory both contain the memory used to store the user's KMurv data and the memory occupied by different data structures within the redis, and RSS refers to the memory allocated by the operating system to the redis instance, which also includes the overhead caused by discontinuous allocation. So ideally, the value of used_memory_rss should be only slightly higher than used_memory. When rss > used, and the difference between the two values is large, it indicates that there is memory fragmentation (internal or external). The ratio of memory fragmentation can be seen by the value of mem_fragmentation_ratio. When used > rss, part of the memory of the Redis is swapped out to swap space by the operating system, in which case the operation may cause significant latency. It can be said that this value greater than 1.5 or less than 1 is problematic. When it is greater than 1.5, you need to choose a machine to restart the server. When it is less than 1, the redis needs to be cleaned up.

Mem_allocator:jemalloc-3.6.0

Redis_version:2.8.19 # redis version number

Redis_git_sha1:00000000 # git SHA1

Redis_git_dirty:0 # git dirty flag

Redis_build_id:78796c63e58b72dc

Redis_mode:standalone # redis operation mode

Os:Linux 2.6.32-431.el6.x86_64 x86mm 64 # os version number

Arch_bits:64 # 64 bit architecture

Multiplexing_api:epoll # call epoll algorithm

Gcc_version:4.4.7 # gcc version number

Process_id:25899 # Server process PID

Random identifier of run_id:eae356ac1098c13b68f2b00fd7e1c9f93b1c6a2c # Redis (for sentinel and clustering)

Tcp_port:6379 # Port number for Redis snooping

Uptime_in_seconds:6419 # # Redis run time (in s)

Uptime_in_days:0 # # Redis run time (in days)

Hz:10

Lru_clock:10737922 # # self-increasing clock in minutes for LRU management

Config_file:/etc/redis/redis.conf # redis configuration file

# Clients

Connected_clients:1 # # the number of connected clients (excluding clients connected through secondary servers) should also be paid attention to. There will be problems when there is a surge or a significant decline. Even if it doesn't operate,

Client_longest_output_list:0 # # the longest output list among currently connected clients

Client_biggest_input_buf:0 # # the largest client currently connected. Output cache

Blocked_clients:0 # the number of clients waiting for blocking commands (BLPOP, BRPOP, BRPOPLPUSH) needs to be monitored

# Memory

Used_memory:2281560 # # the total amount of memory allocated by the Redis allocator in byte

Used_memory_human:2.18M # output the memory consumed by redis in a more friendly format

Used_memory_rss:2699264 # # returns the total amount of memory allocated by Redis (commonly known as resident set size) from an operating system point of view. This value is consistent with the output of top, ps, and other commands, including used_memory and memory fragmentation.

Peak memory consumption of used_memory_peak:22141272 # Redis (in bytes)

Used_memory_peak_human:21.12M # output redis Peak memory usage in a more friendly format

Used_memory_lua:35840 # # amount of memory used by the LUA engine

Mem_fragmentation_ratio:1.18 # = used_memory_rss / used_memory both contain the memory used to store the user's KMurv data and the memory occupied by different data structures within the redis, and RSS refers to the memory allocated by the operating system to the redis instance, which also includes the overhead caused by discontinuous allocation. So ideally, the value of used_memory_rss should be only slightly higher than used_memory. When rss > used, and the difference between the two values is large, it indicates that there is memory fragmentation (internal or external). The ratio of memory fragmentation can be seen by the value of mem_fragmentation_ratio. When used > rss, part of the memory of the Redis is swapped out to swap space by the operating system, in which case the operation may cause significant latency. It can be said that this value greater than 1.5 or less than 1 is problematic. When it is greater than 1.5, you need to choose a machine to restart the server. When it is less than 1, the redis needs to be cleaned up.

Mem_allocator:jemalloc-3.6.0