Introduction to redis info command
redis info commandReturns various information about the Redis server in a format that is easy to interpret (parse) and easy to read. information and statistical values.
By giving the optional parameter section , the command can return only a certain part of the information:
1. server: general Redis server information, including the following fields:
redis_version : Redis server version
redis_git_sha1 : Git SHA1
redis_git_dirty : Git dirty flag
os : Redis server host Operating system
arch_bits: Architecture (32 or 64 bit)
multiplexing_api: The event handling mechanism used by Redis
gcc_version: The GCC version used when compiling Redis
process_id: PID of the server process
run_id: Random identifier of the Redis server (for Sentinel and cluster)
tcp_port: TCP/IP listening port
uptime_in_seconds: The number of seconds that have elapsed since the Redis server was started
uptime_in_days: The number of days that have elapsed since the Redis server was started
lru_clock: A self-increasing clock in minutes, used for LRU Management
2. clients: Connected client information, including the following fields:
connected_clients: The number of connected clients (excluding clients connected through slave servers )
client_longest_output_list: The longest output list among the currently connected clients
client_longest_input_buf: The largest input cache among the currently connected clients
blocked_clients: Waiting for blocking Number of clients for commands (BLPOP, BRPOP, BRPOPLPUSH)
3. memory: memory information, including the following fields:
used_memory: memory allocated by the Redis allocator Total amount, in bytes
used_memory_human: Returns the total amount of memory allocated by Redis in human-readable format
used_memory_rss: From the perspective of the operating system, returns the amount of memory allocated by Redis The total amount of memory (commonly known as the resident set size). This value is consistent with the output of commands such as top and ps.
used_memory_peak: Peak memory consumption of Redis (in bytes)
used_memory_peak_human: Returns peak memory consumption of Redis in human-readable format
used_memory_lua: Lua engine The memory size used (in bytes)
mem_fragmentation_ratio : The ratio between used_memory_rss and used_memory
mem_allocator : Specified at compile time, the memory allocator used by Redis. Can be libc, jemalloc or tcmalloc.
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 means that there is (internal or external) memory fragmentation.
The ratio of memory fragmentation can be seen through the value of mem_fragmentation_ratio.
When used > rss , it means that part of the memory of Redis has been swapped out to the swap space by the operating system. In this case, the operation may cause significant delays.
Because Redis does not have control over how its allocations are mapped to memory pages, high used_memory_rss is often the result of a spike in memory usage.
When Redis releases memory, the allocator may May or may not return memory to the operating system.
If Redis releases memory but does not return the memory to the operating system, then the value of used_memory may not be consistent with the memory usage of Redis displayed by the operating system.
View the value of used_memory_peak to verify whether this occurs.
4. Persistence: RDB and AOF related information
5. Stats: General statistical information
6. Replication: Master/slave replication information
7. cpu: CPU calculation statistics
8. commandstats: Redis command statistics
9. cluster: Redis cluster information
10. keyspace: database-related statistics Information
In addition to the values given above, the parameters can also be the following two:
11, all: return all information
12, default: return to the default Selected information
When the INFO command is called directly without parameters, use default as the default parameter.
Different versions of Redis may add or delete some of the fields returned.
Therefore, a robust client program should be able to skip unrecognized fields and handle missing fields appropriately when parsing the output of the INFO command.
Available versions:
>= 1.0.0
Time complexity:
O(1)
Return value:
Please refer to the test below for details Code:
redis> INFO # Server redis_version:2.5.9 redis_git_sha1:473f3090 redis_git_dirty:0 os:Linux 3.3.7-1-ARCH i686 arch_bits:32 multiplexing_api:epoll gcc_version:4.7.0 process_id:8104 run_id:bc9e20c6f0aac67d0d396ab950940ae4d1479ad1 tcp_port:6379 uptime_in_seconds:7 uptime_in_days:0 lru_clock:1680564 # Clients connected_clients:1 client_longest_output_list:0 client_biggest_input_buf:0 blocked_clients:0 # Memory used_memory:439304 used_memory_human:429.01K used_memory_rss:13897728 used_memory_peak:401776 used_memory_peak_human:392.36K used_memory_lua:20480 mem_fragmentation_ratio:31.64 mem_allocator:jemalloc-3.0.0 # Persistence loading:0 rdb_changes_since_last_save:0 rdb_bgsave_in_progress:0 rdb_last_save_time:1338011402 rdb_last_bgsave_status:ok rdb_last_bgsave_time_sec:-1 rdb_current_bgsave_time_sec:-1 aof_enabled:0 aof_rewrite_in_progress:0 aof_rewrite_scheduled:0 aof_last_rewrite_time_sec:-1 aof_current_rewrite_time_sec:-1 # Stats total_connections_received:1 total_commands_processed:0 instantaneous_ops_per_sec:0 rejected_connections:0 expired_keys:0 evicted_keys:0 keyspace_hits:0 keyspace_misses:0 pubsub_channels:0 pubsub_patterns:0 latest_fork_usec:0 # Replication role:master connected_slaves:0 # CPU used_cpu_sys:0.03 used_cpu_user:0.01 used_cpu_sys_children:0.00 used_cpu_user_children:0.00
For more redis knowledge, please pay attention to the redis introductory tutorial column.
The above is the detailed content of Introduction to redis info command. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Redis cluster mode deploys Redis instances to multiple servers through sharding, improving scalability and availability. The construction steps are as follows: Create odd Redis instances with different ports; Create 3 sentinel instances, monitor Redis instances and failover; configure sentinel configuration files, add monitoring Redis instance information and failover settings; configure Redis instance configuration files, enable cluster mode and specify the cluster information file path; create nodes.conf file, containing information of each Redis instance; start the cluster, execute the create command to create a cluster and specify the number of replicas; log in to the cluster to execute the CLUSTER INFO command to verify the cluster status; make

How to clear Redis data: Use the FLUSHALL command to clear all key values. Use the FLUSHDB command to clear the key value of the currently selected database. Use SELECT to switch databases, and then use FLUSHDB to clear multiple databases. Use the DEL command to delete a specific key. Use the redis-cli tool to clear the data.

To read a queue from Redis, you need to get the queue name, read the elements using the LPOP command, and process the empty queue. The specific steps are as follows: Get the queue name: name it with the prefix of "queue:" such as "queue:my-queue". Use the LPOP command: Eject the element from the head of the queue and return its value, such as LPOP queue:my-queue. Processing empty queues: If the queue is empty, LPOP returns nil, and you can check whether the queue exists before reading the element.

Using the Redis directive requires the following steps: Open the Redis client. Enter the command (verb key value). Provides the required parameters (varies from instruction to instruction). Press Enter to execute the command. Redis returns a response indicating the result of the operation (usually OK or -ERR).

Using Redis to lock operations requires obtaining the lock through the SETNX command, and then using the EXPIRE command to set the expiration time. The specific steps are: (1) Use the SETNX command to try to set a key-value pair; (2) Use the EXPIRE command to set the expiration time for the lock; (3) Use the DEL command to delete the lock when the lock is no longer needed.

The best way to understand Redis source code is to go step by step: get familiar with the basics of Redis. Select a specific module or function as the starting point. Start with the entry point of the module or function and view the code line by line. View the code through the function call chain. Be familiar with the underlying data structures used by Redis. Identify the algorithm used by Redis.

Redis data loss causes include memory failures, power outages, human errors, and hardware failures. The solutions are: 1. Store data to disk with RDB or AOF persistence; 2. Copy to multiple servers for high availability; 3. HA with Redis Sentinel or Redis Cluster; 4. Create snapshots to back up data; 5. Implement best practices such as persistence, replication, snapshots, monitoring, and security measures.

Use the Redis command line tool (redis-cli) to manage and operate Redis through the following steps: Connect to the server, specify the address and port. Send commands to the server using the command name and parameters. Use the HELP command to view help information for a specific command. Use the QUIT command to exit the command line tool.
