What is the principle of Redis data structure?
RedisDb
The Redis server has 16 databases by default, and one database corresponds to one RedisDB data structure.
typedef struct redisDb { dict *dict; dict *expires; dict * blocking_keys; dict * ready_keys; dict * watched_keys; ...... }
dict: key space hash table, used to store all key-value pairs
expires: expiration time hash table, used to store the expiration of keys Time
blocking_keys: keys in blocked state and corresponding client
ready_keys: keys in unblocked state and corresponding client, and blocking_keys The attributes are relative
watched_keys: watch key and corresponding client, mainly used for transactions
RedisObject
Redis key The values are all redisObject objects. Every time we create a new key-value pair in the Redis database, a redisObject object for the key name and a redisObject object for the key value will be generated
trpedef struct RedisObject { int4 type; int4 encoding; void *ptr; int24 lru; int32 refcount; }
Field | Description | Explanation |
---|---|---|
type | is used to represent the type corresponding to Redis | String, list, hash, set, zset, stream, etc. are represented by enumerations |
encoding | Internal encoding | int , embstr, raw, hashtable, quicklist, ziplist, intset, skiplist, etc., represented by enumeration |
lru | 24 bits, optional LFU or LRU | When it is LRU, it represents the last access time; when it is LFU, the high 16 bits are used to represent the access time at the minute level, and the low 8 bits are used to represent the access frequency. The increase in frequency uses a probability algorithm, the base The larger it is, the harder it is to increase; when the access time is updated, there is a certain probability that the access frequency will be attenuated. (Common to both) Access time is a modulo of a number, and the current time is also modulo. If the current time is greater than the access time, it is the difference between the two numbers; if the current time is less than the access time, it is the current time plus the modulus and the access time. The difference |
refcount | Reference count | The initial value is 1, which is of little reference significance in practical applications |
ptr | Pointer, occupies 8 bytes, points to the address of the data | dict, expires, etc., the pointer points to the same address |
object
command is the related operation on RedisObject.
Modify the memory elimination strategy
object idletime key # Returns the idle time of the key, that is, the approximate description of the time since the last time the key was read and written. It is not available in lfu mode
config set maxmemory-policy volatile-lfu # 修改内存淘汰策略 set name zhangsan object freq name # 获取计数值,仅lfu模式下可用,初始化为5 get name object freq name # 再次访问,返回为6
int
When the string value is an integer and is less than or equal to the maximum value of long, the encoding is int type, and ptr directly points to the int type address
embstr and raw
Redis The string is called SDS (Simple Dynamic String, simple string), corresponding to the key, non-integer String value
trpedef struct SDS { int8 capacity; // 数组容量 int8 len; // 实际长度 int8 flags; byte[] content; // 数组内容 }
It can be seen that SDS is similar to Java's ArrayList structure, and it is also Allocate an initial length and expand it when the length exceeds. Redis stipulates that the length of the string cannot exceed 512M.
When the length is particularly short, use embstr form to store; when the length exceeds 44 bytes, use raw form to store.
It is known that the maximum allocation unit of the memory allocator is 64 bytes, RedisObject occupies 16 bytes, the SDS identifier occupies 3 bytes, and a string ending with NULL requires one byte, so when the string length When it is less than or equal to 44, memory only needs to be allocated once. RedisObject and SDS are in the same memory unit. We call this data structure embstr, while those that are not in the same memory unit are called raw.
dict
dict (encoding is hashtable type, dictionary) corresponds to hash, set, zset (used to store the mapping between value and score) collection.
dict is similar to Java's HashMap structure. The difference is that HashMap expansion requires an array, then traverses it, re-hashes the old data and hangs it under the array. As a single-threaded Redis, it is difficult To withstand such a time-consuming process, it uses two arrays, returns first, and then moves the data bit by bit when it is free. After the move is completed, the old data is cleared. We call this process progressive rehash .
typedef struct dict { dictht ht[2]; }
The above is the detailed content of What is the principle of Redis data structure?. 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

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.

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.

On CentOS systems, you can limit the execution time of Lua scripts by modifying Redis configuration files or using Redis commands to prevent malicious scripts from consuming too much resources. Method 1: Modify the Redis configuration file and locate the Redis configuration file: The Redis configuration file is usually located in /etc/redis/redis.conf. Edit configuration file: Open the configuration file using a text editor (such as vi or nano): sudovi/etc/redis/redis.conf Set the Lua script execution time limit: Add or modify the following lines in the configuration file to set the maximum execution time of the Lua script (unit: milliseconds)

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.

There are two types of Redis data expiration strategies: periodic deletion: periodic scan to delete the expired key, which can be set through expired-time-cap-remove-count and expired-time-cap-remove-delay parameters. Lazy Deletion: Check for deletion expired keys only when keys are read or written. They can be set through lazyfree-lazy-eviction, lazyfree-lazy-expire, lazyfree-lazy-user-del parameters.

In Debian systems, readdir system calls are used to read directory contents. If its performance is not good, try the following optimization strategy: Simplify the number of directory files: Split large directories into multiple small directories as much as possible, reducing the number of items processed per readdir call. Enable directory content caching: build a cache mechanism, update the cache regularly or when directory content changes, and reduce frequent calls to readdir. Memory caches (such as Memcached or Redis) or local caches (such as files or databases) can be considered. Adopt efficient data structure: If you implement directory traversal by yourself, select more efficient data structures (such as hash tables instead of linear search) to store and access directory information

Redis counter is a mechanism that uses Redis key-value pair storage to implement counting operations, including the following steps: creating counter keys, increasing counts, decreasing counts, resetting counts, and obtaining counts. The advantages of Redis counters include fast speed, high concurrency, durability and simplicity and ease of use. It can be used in scenarios such as user access counting, real-time metric tracking, game scores and rankings, and order processing counting.
