Detailed description of Redis info Parameters

Detailed description of Redis info Parameters

The official Redis website has clearly explained info. Refer to the documentation. As you can see, the output result of info is several pieces, including Servers, Clients, and Memory. You can specify a piece of data to be output through the parameters following info.

Redis 2.4.10, There is no multipart output, and it is impossible to control the output of a piece according to the Add option described above, and then upgraded2.6.7And2.6.8All versions are reported.Segment FaultSegment error. It cannot be solved after searching for half a day. I asked in the Gentoo forum that it should be a bug.

Then update the portage tree and replace it2.6.9Version.

View stat

Root @ localhost :~ # Redis-cli info stats

# Stats

Total_connections_received: 558158

Total_commands_processed: 917

Instantaneous_ops_per_sec: 0

Total_net_input_bytes: 19652432

Total_net_output_bytes: 23901681

Instantaneous_input_kbit: 0.00

Instantaneous_output_kbit: 0.00

Rejected_connections: 0

Sync_full: 0

Sync_partial_ OK: 0

Sync_partial_err: 0

Expired_keys: 156

Evicted_keys: 0

Keyspace_hits: 496

Keyspace_misses: 188

Pubsub_channels: 0

Pubsub_patterns: 0

Latest_fork_usec: 179

Migrate_cached_sockets: 0

Below is the output for info

# Reference: http://redis.io/commands/info

#

#

# Server

Redis_version: 2.6.9

Redis_git_sha1: 00000000

Redis_git_dirty: 0

Redis_mode: standalone

OS: Linux 3.4.9-gentoo x86_64

Arch_bits: 64

Multiplexing_api: epoll # redis event Loop Mechanism

Gcc_version: 4.6.3

Process_id: 18926

Run_id: df8ad7574f3ee5136e8be94aaa6602a0079704cc # identifies the random value of the redis server

Tcp_port: 6379

Uptime_in_seconds: 120 # redis server startup time (unit: s)

Uptime_in_days: 0 # Start Time of the redis server (unit: d)

Lru_clock: 321118 # Clock incrementing every minute, for LRU management TODO is not clear about how to calculate

 

# Clients

Connected_clients: 3 # number of connected clients

Client_longest_output_list: 0 # The maximum output list of the current client connection TODO

Client_biggest_input_buf: 0 # maximum input buffer TODO for the current client connection

Blocked_clients: 0 # Number of blocked clients

 

# Memory

Used_memory: 573456 # memory usage, in B

Used_memory_human: 560.02 K # use memory for human read display

Used_memory_rss: 1798144 # Memory allocated by the system to redis (that is, resident memory)

Used_memory_peak: 551744 # memory usage peak size

Used_memory_peak_human: 538.81 K # display the memory usage peak value of human read

Used_memory_lua: 31744 # memory used by lua Engine

Mem_fragmentation_ratio: 3.14 # used_memory_rss/used_memory ratio. Generally, used_memory_rss is slightly higher than used_memory. When there are many memory fragments, mem_fragmentation_ratio is large, which can reflect whether there are many memory fragmentation

Mem_allocator: jemalloc-3.3.1 # Memory distributor

 

# Persistence

##########################

# Two persistence mechanisms: rdb and aof redis

#

# Rdb uses the configuration file to set the number of changes to the save time.

# Save the last modified data to the database after reaching the set metrics

# If a crash occurs in the middle, the data will be lost

# This policy is called a snapshot.

#

# Aof constantly writes write operations to a log-like file

# But the shadow response can

# Appendfsync always and appendfsync eversec

# The former is synchronized for each write operation, with high data security, but especially performance consumption

# The latter is synchronized once per second. If a crash occurs, the data may be lost for 1 s.

##########################

Loading: 0 #

Rdb_changes_since_last_save: 0 # rdb changes since the last dump

Rdb_bgsave_in_progress: 0 # identify whether rdb save is in progress

Rdb_last_save_time: 1366359865 # timestamp of the last save

Rdb_last_bgsave_status: OK # status of the last save operation

Rdb_last_bgsave_time_sec:-1 # Time used for the last rdb save operation (unit: s)

Rdb_current_bgsave_time_sec:-1 # the time used if the rdb save operation is in progress

----------------------------

Aof_enabled: 0 # Whether to enable aof. It is disabled by default.

Aof_rewrite_in_progress: 0 # indicates whether the rewrite operation of aof is in progress

Aof_rewrite_scheduled: 0 # identify whether to execute after the rdb save operation is complete

Aof_last_rewrite_time_sec:-1 # Time used for the last rewrite operation (unit: s)

Aof_current_rewrite_time_sec:-1 # If the rewrite operation is in progress, record the time used

Aof_last_bgrewrite_status: OK # status of the last rewrite operation

-----------------------------

# Some info information added after aof is enabled

Aof_current_size: 0 # aof current size

Aof_base_size: 0 # aof the size of the last startup or rewrite

Aof_pending_rewrite: 0 # Same as aof_rewrite_scheduled

Aof_buffer_length: 0 # aof buffer size

Aof_rewrite_buffer_length: 0 # aof rewrite buffer size

Aof_pending_bio_fsync: 0 # Number of fsync tasks waiting in the background IO queue

Aof_delayed_fsync: 0 # delayed fsync counter TODO

-----------------------------

 

# Stats

Total_connections_received: 7 # Total number of connections established since startup

Total_commands_processed: 7 # Total number of self-started commands

Instantaneous_ops_per_sec: 0 # Number of commands executed per second

Rejected_connections: 0 # Number of connections denied due to the maximum client connection book limit

Expired_keys: 0 # Total number of keys that have expired since startup

Evicted_keys: 0 # number of keys evicted due to memory size restrictions

Keyspace_hits: 0 # number of keys successfully found in main dictionary (todo)

Keyspace_misses: 0 # Same as above, number of keys not found

Pubsub_channels: 0 # Number Of Publish/subscribe Channels

Pubsub_patterns: 0 # Number Of Publish/subscribe Modes

Latest_fork_usec: 0 # Time used by the last fork operation (unit: ms)

##########################

# Pubsub is a message transmission method, which can be either channel or mode.

# The message does not support persistence. If a message is disconnected and connected, the previous message will be lost.

# A channel is subscribed to by specifying a fixed channel through SUBSCRIBE

# Mode refers to the subscription of Related Channels matching the specified mode through PSUBSCRIBE mode matching

##########################

 

# Replication

Role: master # role

Connected_slaves: 1 # number of connected slave Databases

Slave0: 127.0.0.1, 7777, online

-----------------------------

Role: slave

Master_host: 127.0.0.1

Master_port: 6379

Master_link_status: up

Master_last_io_seconds_ago: 4

Master_sync_in_progress: 0 # identify that the master redis is synchronizing to the slave redis

Slave_priority: 100

Slave_read_only: 1

Connected_slaves: 0

 

 

# CPU

Used_cpu_sys: 0.00 # redis server's sys cpu usage

Used_cpu_user: 0.12 # redis server user cpu usage

Used_cpu_sys_children: 0.00 # sys cpu usage of background processes

Used_cpu_user_children: 0.00 # user cpu usage of background processes

 

# Keyspace

Db0: keys = 2, expires = 0

Db1: keys = 1, expires = 0

You may also like the following articles about Redis. For details, refer:

Install and test Redis in Ubuntu 14.04

Basic configuration of Redis master-slave Replication

Redis cluster details

Install Redis in Ubuntu 12.10 (graphic explanation) + Jedis to connect to Redis

Redis series-installation, deployment, and maintenance

Install Redis in CentOS 6.3

Learning notes on Redis installation and deployment

Redis. conf

Redis details: click here
Redis: click here

This article permanently updates the link address: