Redis Info Parameter Summary (RPM)

The Redis official website has already explained the relative clarity of the info, reference documents.

You can see that the output of info is divided into several blocks, with servers, clients, memory, and so on, you can specify the output of a piece of data by following these parameters through info.

I just started in the Gentoo installed in the default version 2.4.10 , and no block output, are squeezed into a heap, and can not be added to the above-mentioned option to control the output of a piece, later upgraded to 2.6.7 and 2.6.8 the version, are reported Segment Fault section error, find a half day can not solve, Also asked in the Gentoo forum, it should be a bug. Later update the Portage tree, and then change 2.6.9 the version, there is no problem (my colleague happened to also encounter this problem, today I let him upgrade to 2.6.9, also resolved)

Here is the output for info on the next note, because the Redis understanding of the not deep, there may be errors, later learn more and then gradually improve.

# Reference: http://redis.io/commands/info### Serverredis_version:2.6.9redis_git_sha1:00000000redis_git_dirty:0redis_ Mode:standaloneos:Linux 3.4.9-gentoo x86_64arch_bits:64multiplexing_api:epoll# Redis's event loop mechanism gcc_version : 4.6.3process_id:18926run_id:df8ad7574f3ee5136e8be94aaa6602a0079704cc# identifies a random value for Redis server Tcp_port:6379uptime_in_ seconds:120# Redis Server start time (unit s) uptime_in_days:0# Redis server startup time (in units D) lru_clock:321118# clock incrementing every minute, for LRU management TODO is not clear how to calculate the number of # clientsconnected_clients:3# connected clients client_longest_output_list:0# Maximum output list of current client connections todoclient_biggest_input_buf:0# maximum input buffer for current client connections todoblocked_clients:0# number of blocked clients # Memoryused_ memory:573456# uses memory, unit bused_memory_human:560.02k# Human read display uses memory used_memory_rss:1798144# The amount of memory that the system allocates to Redis (that is, resident memory) used_memory_peak:551744# the peak size of memory usage used_memory_peak_human:538.81k# Human read shows memory usage spikes used_ memory_lua:31744# LUA engine uses memory mem_fragmentation_ratio:3.14# used_memory_rss/used_memory scale, in general, Used_memory_ RSS is slightly higher than used_memory, and when memory fragmentation is high, Mem_fragMentation_ratio will be larger and can reflect memory fragmentation if many mem_allocator:jemalloc-3.3.1# memory allocator # persistence########################### Two persistence mechanisms for the RDB and AoF Redis # # The RDB is the number of changes to the time that the save is set by the config file # Save to db# if there is a crash in the middle, the data is lost # This strategy is called Snapshot # # AOF is a continuous write operation to write to a similar log file # but it will affect the # Appendfsync always and Appendfsync eversec# the former each write operation is synchronous, high data security, but special consumption performance # The latter synchronization per second, If crash occurs, you may lose 1s of data ######################### #loading: 0#rdb_changes_since_last_save:0# changes to the RDB since the last dump Rdb_ bgsave_in_progress:0# identifies if the Rdb save is in progress rdb_last_save_time:1366359865# the last save timestamp rdb_last_bgsave_status:ok# Last save Operation State rdb_last_bgsave_time_sec:-1# the time (in units s) used by the last RDB save operation rdb_current_bgsave_time_sec:-1# If the RDB save operation is in progress, Is the time used----------------------------aof_enabled:0# whether the aof is turned on, the default is not turned on aof_rewrite_in_progress:0# Identifies whether the rewrite operation of AOF is in progress aof_rewrite_scheduled:0# the identity will be executed after the RDB save operation ends aof_last_rewrite_time_sec:-1# Time used by last rewrite operation (unit s) aof_current_rewrite_time_sec:-1 # If the rewrite operation is in progress, the time used is recorded aof_last_bgrewrite_status:ok# Status of Last rewrite Operation-----------------------------# Open aSome info added after aof_current_size:0# aof current size aof_base_size:0# aof last boot or rewrite size aof_pending_rewrite:0# same as above aof_ rewrite_scheduledaof_buffer_length:0# aof buffer size aof_rewrite_buffer_length:0# aof rewrite buffer size aof_pending_ bio_fsync:0# the number of fsync tasks waiting in the background IO queue aof_delayed_fsync:0# deferred fsync counters TODO-----------------------------# Statstotal_ connections_received:7# total number of connections since startup total_commands_processed:7# The total number of RUN commands since startup instantaneous_ops_per_sec:0# Number of commands executed per second rejected_connections:0# because of the maximum client connection book limit, the number of rejected connections expired_keys:0# the total number of keys that have expired since startup evicted_keys:0# because of memory size limitations, and the number of keys evicted keyspace_hits:0# in main dictionary (TODO) successfully found in the number of key keyspace_misses:0#, the number of key not found pubsub_channels:0# released /number of subscribed channels pubsub_patterns:0# number of publish/subscribe modes latest_fork_usec:0# The last time the fork operation was used (unit ms) ########################### PubSub is a way of message transmission, divided into channels and patterns of two # messages do not support persistence, the message is interrupted after the connection, the front of the message will be lost # channel refers to a fixed channel by subscribe to subscribe to the # A pattern is a channel ########################### replicationrole:master# role that subscribes to a related matching pattern by psubscribe pattern matching connected_slaves:1# The number of connections from the library slave0:127.0.0.1,7777,online-----------------------------Role:slavemaster_host:127.0.0.1master_port:6379master_link_status:upmaster_last_io_seconds_ ago:4master_sync_in_progress:0# Identity Master Redis is synchronizing to from redisslave_priority:100slave_read_only:1connected_slaves:0# cpuused_cpu_sys:0.00# the SYS CPU usage of REDIS server used_cpu_user:0.12# the user CPU usage of Redis server used_cpu_sys_children:0.00# SYS CPU utilization of the background process used_cpu_user_children:0.00# user CPU usage of the background process # Keyspacedb0:keys=2,expires=0db1:keys=1,expires=0

Summary of Redis info parameters (GO)