How to use Bitmap in Redis
In the daily development process, there are often some bool type data that need to be accessed. For example, if you record the number of times a user has checked in within a year, the number of times a user has checked in is 1, and the number of times a user has not signed is 0. If key-value is used for storage, each user will be recorded 365 times. When there are hundreds of millions of users, the storage space required will be very huge. To solve this problem, you can use bitmaps in redis.
Bitmap (bitmap) also belongs to the string data type. A string type value in Redis can store up to 512 MB of content. Each string is composed of multiple bytes, and each byte is composed of 8 Bits. The bitmap structure uses "bits" to achieve storage. It achieves the purpose of data access by setting bits to 0 or 1, which greatly increases the number of value storage, and its storage upper limit is 2^32.
A bitmap is essentially an ordinary byte string, that is, a bytes array. This bitmap array can be processed by using the getbit/setbit command, and its structure is as follows:
Bitmaps are usually used for some specific applications, such as tracking user check-ins or logins frequency. The above picture shows the number of check-ins a user has come to the website within 10 days. 1 represents a sign-in and 0 represents a non-check-in. This way, the user's activity level can be easily counted. Using a bitmap to record each record only occupies one bit, which greatly reduces the memory space usage compared to using strings directly.
Redis officials also conducted an experiment. They simulated a system with 128 million users, and then used Redis bitmaps to count the "average number of daily users". The final time spent was approximately is 50ms and only takes up 16 MB of memory.
Bitmap application principle
If string type storage is used, a website must record a user's check-in record for one year, then 365 key-value pairs are required. If bitmap storage is used, 1 is stored when the user signs in, otherwise 0 is stored. In the end, a storage result like 00010101... will be generated, in which each day's record only occupies one bit, and one year is 365 bits, which is about 46 bytes. If you only want to count the number of days that users have signed in, then count the number of 1.
The advantage of bitmap operations is that compared to strings, it is not only highly efficient, but also very space-saving.
The bit array of Redis is automatically expanded. If an offset position is set beyond the existing content range, the bit array will be automatically expanded.
Common bitmap commands
1) SETBIT command
is used to set or clear the value of a certain bit, and its return value is the value stored in the original bit. In the initial state, all bits of key are 0. The example is as follows:
SETBIT key offset value
where offset represents the offset, starting from 0. Examples are as follows:
127.0.0.1:6379> SET user:1 a OK #设置偏移量offset为0 127.0.0.1:6379> SETBIT user:1 0 1 (integer) 0 #当对应位的字符是不可打印字符,redis会以16进制形式显示 127.0.0.1:6379> GET user:1 "\xe1"
2) GETBIT command
is used to get the value of a certain bit. Examples are as follows:
127.0.0.1:6379> GETBIT user:1 0 (integer) 1
When the offset offset is greater than the length of the string, or when the key does not exist, 0 is returned.
redis> EXISTS bits (integer) 0 redis> GETBIT bits 100000 (integer) 0
3) The BITCOUNT command
counts the number of values that are 1 in the specified position interval. The syntax format is as follows:
BITCOUNT key [start end]
The example is as follows:
127.0.0.1:6379> BITCOUNT user:1 (integer) 8
Just specify the start and end parameters to count only specific bytes. The start and end parameters are similar to the parameters of the GETRANGE command. Negative numbers can be used. For example, -1 represents the first digit from the last, and -2 represents the second digit from the last. .
4) Redis Bitop command
Perform bit operations on one or more string keys that store binary bits, and save the results to destkey
The operation can It is any one of the four types: AND, OR, NOT, The result is saved to destkey.
BITOP OR destkey key [key …] , perform logical OR on one or more keys, and save the result to - destkey .
BITOP XOR destkey key [key …], perform logical XOR on one or more keys, and save the result to destkey.
BITOP NOT destkey key, perform logical negation on the given key and save the result to destkey.
Except for NOT operations, other operations can accept one or more keys as input.
Scenario
Statistics on active users for the day
Daily active statistics create a bitmap key, and when the user is active, set the
corresponding one based on the offset of the user id The bit is 1User sign-in
Each user creates a bitmap key, based on a certain day, and the number of subsequent days from this day is the offset,
The above is the detailed content of How to use Bitmap in Redis. 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.

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.

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.

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
