Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Redis 4.0 info details

2025-04-06 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

Redis_version:4.0.2 # redis version

Redis_git_sha1:00000000 # Git SHA1

Redis_git_dirty:0 # Git dirty flag

Redis_build_id:4cd4fc541375a86a # redis build id

Redis_mode:standalone # operating mode, stand-alone or cluster

Os:Linux 2.6.32-the host operating system for 696.10.1.el6.x86_64 x86room64 # redis server

Arch_bits:64 # architecture (32 or 64 bit)

Event handling mechanism used by multiplexing_api:epoll # redis

Atomicvar_api:sync-builtin # GNU Compiler Collection used by redis

Gcc_version:4.4.7 # gcc version used when compiling redis

Process_id:12099 # pid of the redis server process

Random identifier of the run_id:76d165405279aa89a3e9e41bffeae51542d3dc4d # redis server (for sentinel and clustering)

Tcp_port:6379 # redis server listening port

Total uptime_in_seconds:3881741 # redis server startup time (in seconds)

Total uptime_in_days:44 # redis server startup time (in days)

Hz:10 # redis internal scheduling (shutting down the client of timeout, deleting expired key, etc.) frequency, the program requires serverCron to run 10 times per second.

Lru_clock:14233104 # self-incremented clock for LRU management, which is updated once for 100ms (hz=10, so a scheduled task is performed per 1000ms/10=100ms).

Config_file:/data/redis/conf/redis.conf # profile path

# Clients (connected client information)

Connected_clients:1081 # number of connected clients (excluding clients connected through slave)

Client_longest_output_list:0 # the longest output list among the currently connected clients, use the client list command to observe the maximum value of the omem field

Client_biggest_input_buf:0 # the maximum input cache among the currently connected clients. Use the client list command to observe the maximum values of qbuf and qbuf-free fields.

Blocked_clients:0 # number of clients waiting for blocking commands (BLPOP, BRPOP, BRPOPLPUSH)

# Memory (memory information)

Used_memory:327494024 # the total amount of memory allocated by the redis allocator in bytes

Used_memory_human:312.32M # returns the total amount of memory allocated by redis in a human readable format

Used_memory_rss:587247616 # returns the total amount of memory allocated by redis (commonly known as resident set size) from an operating system perspective. This value is consistent with the output of the top command

Peak memory consumption for used_memory_peak:1866541112 # redis (in bytes)

Used_memory_peak_human:1.74G # returns the peak memory consumption of redis in a human-readable format

The amount of memory used by the used_memory_lua:35840 # lua engine in bytes

The ratio between mem_fragmentation_ratio:1.79 # used_memory_rss and used_memory. Less than 1 indicates the use of swap, and greater than 1 indicates more fragments.

The memory allocator used by the redis specified by mem_allocator:jemalloc-3.6.0 # at compile time. It can be libc, jemalloc, or tcmalloc

Active_defrag_running # indicates that no active defrag task is running, and 1 indicates that there is an active defrag task running (defrag: indicates memory defragmentation)

Lazyfree_pending_objects # 0 indicates that there are no pending objects with delayed release (and some data translation is not lazily deleted).

# Persistence (persistence related information of rdb and aof)

Whether the loading:0 # server is loading persistence files

Rdb_changes_since_last_save:28900855 # since the last rdb file was successfully generated, the number of write commands, that is, how many write commands have not been persisted

Whether the rdb_bgsave_in_progress:0 # server is creating a rdb file

Rdb_last_save_time:1482358115 # the timestamp of the last successful creation of the rdb file. Current timestamp-how many seconds did rdb_last_save_time= fail to generate the rdb file

Rdb_last_bgsave_status:ok # whether the last rdb persistence was successful

Rdb_last_bgsave_time_sec:2 # the number of seconds it took to successfully generate a rdb file last time

Rdb_current_bgsave_time_sec:-1 # if the server is creating a rdb file, then this domain records the number of seconds that the current creation operation has taken

Whether aof_enabled:1 # has aof enabled

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

Aof_rewrite_scheduled:0 # rewrite task planning. When the client sends a bgrewriteaof instruction, if the current rewrite child process is executing, the bgrewriteaof requested by the client will be changed into a scheduled task, and the rewrite will be executed after the AOF child process ends

Aof_last_rewrite_time_sec:-1 # how long did the last aof rewrite take

Aof_current_rewrite_time_sec:-1 # if the rewrite operation is in progress, record the time used (in seconds)

Aof_last_bgrewrite_status:ok # status of the last bgrewriteaof operation

Aof_last_write_status:ok # Last aof write status

How many modifications (including read buffer, write buffer, data modification, etc.) performed by the parent process compared to the child process during the aof_last_cow_size # AOF process.

Aof_current_size:4201740 # aof current size

The size of the aof file when the aof_base_size:4201687 # server starts or after aof rewrites the last execution

Does aof_pending_rewrite:0 # have aof rewrite operations that are performed after waiting for the rdb file to be created?

Size of aof_buffer_length:0 # aof buffer

Size of aof_rewrite_buffer_length:0 # aof rewrite buffer

The number of fsync calls waiting to be executed in the aof_pending_bio_fsync:0 # backend fsync O queue

Aof_delayed_fsync:0 # number of fsync calls delayed

# Stats (General Statistics)

Total_connections_received:209561105 # number of newly created connections. If there are too many newly created connections, excessive creation and destruction of connections will have an impact on performance, indicating that short connections are serious or there are problems with the use of connection pooling. You need to investigate the connection settings of the code.

Number of commands processed by total_commands_processed:2220123478 # redis

Instantaneous_ops_per_sec:279 # redis the number of commands executed per second in real time within the current qps,redis

Total_net_input_bytes:118515678789 # redis network ingress traffic bytes

Total_net_output_bytes:236361651271 # redis network egress traffic bytes

Instantaneous_input_kbps:13.56 # redis Network Portal kps

Instantaneous_output_kbps:31.33 # redis Network Egress kps

The number of connections rejected by rejected_connections:0 #, the number of redis connections reaching the maxclients limit, and the number of new connections rejected

Sync_full:1 # number of successful master-slave complete synchronization

Sync_partial_ok:0 # number of successful master-slave synchronization

Sync_partial_err:0 # number of master-slave synchronization failures

The number of expired key since expired_keys:15598177 # was run

The number of key excluded (after exceeding maxmemory) since evicted_keys:0 # was run

Keyspace_hits:1122202228 # hit times

Keyspace_misses:577781396 # number of hits

Pubsub_channels:0 # number of channels currently in use

Pubsub_patterns:0 # the number of modes currently in use

Latest_fork_usec:15679 # the time spent blocking the redis process in the last fork operation (in microseconds)

Whether migrate_cached_sockets:0 # has cached the connection to this address

Slave_expires_tracked_keys # number of key expired from the instance

Active_defrag_hits # number of active defragmentation hits

Active_defrag_misses # number of active defragmentation misses

Active_defrag_key_hits # active defragmentation key hits

Active_defrag_key_misses # number of active defragmentation key misses

# Replication (master-slave information, information displayed on master)

The role of the role:master # instance, which is master or slave

Number of slave instances connected to connected_slaves:1 #

Slave0:ip=192.168.64.104,port=9021,state=online,offset=6713173004,lag=0 # lag how many seconds did not send the REPLCONF command to the master library from the slave library

Master_repl_offset:6713173145 # master-slave synchronization offset. If this value is the same as the above offset, it means that the master-slave is consistent without delay.

Repl_backlog_active:1 # whether the replication backlog buffer is enabled

Repl_backlog_size:134217728 # replication backlog buffer size

Repl_backlog_first_byte_offset:6578955418 # size of the offset in the copy buffer

Repl_backlog_histlen:134217728 # this value is equal to master_repl_offset-repl_backlog_first_byte_offset and does not exceed the size of repl_backlog_size

# Replication (master-slave information, information displayed on slave)

The role of the role:slave # instance, which is master or slave

Master_host:192.168.64.102 # ip of the master corresponding to this node

Master_port:9021 # port of the master corresponding to this node

The master_link_status:up # server can view the synchronization status between it and master, which indicates down when replication is disconnected.

How many seconds does the master_last_io_seconds_ago:0 # master library not send data to the slave library?

Master_sync_in_progress:0 # whether the slave server is synchronizing with the master server

Slave_repl_offset:6713173818 # slave replication offset

Slave_priority:100 # slave priority

Slave_read_only:1 # whether to set read-only from the library

Number of slave instances connected to connected_slaves:0 #

Master_repl_offset:0

Repl_backlog_active:0 # whether the replication backlog buffer is enabled

Repl_backlog_size:134217728 # replication backlog buffer size

Repl_backlog_first_byte_offset:0 # size of the offset in the copy buffer

Repl_backlog_histlen:0 # this value is equal to master_repl_offset-repl_backlog_first_byte_offset and does not exceed the size of repl_backlog_size

# CPU (CPU Computing Statistics)

Used_cpu_sys:96894.66 # accumulates the sum of CPU occupied by all redis main processes in the core mindset

Used_cpu_user:87397.39 # accumulates the sum of CPU occupied by all redis main processes in user mode

Used_cpu_sys_children:6.37 # accumulates the sum of CPU occupied by the background process in the core mentality

Used_cpu_user_children:52.83 # accumulates the sum of the CPU occupied by the background process in user mode

# Commandstats (execution statistics for different types of commands)

Cmdstat_get # get Command Statistics

Cmdstat_set # set Command Statistics

Cmdstat_ping # ping Command Statistics

Cmdstat_del # Del Command Statistics

Cmdstat_psync # Psync Command Statistics

Cmdstat_keys # Keys Command Statistics

Cmdstat_hmset # Hmset Command Statistics

Cmdstat_command # Command Command Statistics

Cmdstat_info # Info Command Statistics

Cmdstat_replconf # Replconf Command Statistics

Cmdstat_client # Client Command Statistics

Cmdstat_hgetall # Hgetall Command Statistics

# call the total CPU time consumed by usec for each command execution (unit microsecond) and the average CPU time consumed each time (unit microsecond)

# Cluster (cluster related information)

Whether cluster mode is enabled for cluster_enabled:0 # instance. 0 means it is not enabled.

# Keyspace (database-related statistics)

The number of key of db0:keys=5,expires=0,avg_ttl=0 # db0, and the number of key with lifetime, the average survival time

Transferred from: http://blog.itpub.net/15498/viewspace-2644200/

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report