Redis stores logs and popular articles
A variety of data structures can be implemented using the Redis list data type, which can be regarded as an index array in PHP. It can implement a variety of data structures such as stacks, queues, and message queues. Today, I would like to introduce to you how to use redis to save system logs and popular article lists.
Storing logs
As we all know, nginx logs will not be automatically cut by default. They will always be stored in a file and appended to. We need to do the log cutting operation ourselves. In addition to nginx, logs are used in many places. When something goes wrong, logs are one of the main ways we look for clues.
We now plan to write the system logs to redis. Daily logs will be recorded in a list to prevent a single log file from being too large.
The basic idea is to write daily log information into a separate list, and then do a scheduled task. The function of the scheduled task is to take out the log list from 1 month ago and persist it. to a text file, and then delete the log list from 1 month ago in redis to prevent redis from occupying too much memory.
You can use the compression function to compress log information and reduce memory usage. In addition, maintain a list to store the key names of the log list to facilitate retrieving the key names of the log list. The pseudocode for storing logs is as follows:
$log = ... // 日志信息 // 日志列表键名 $key = 'log:'.strtotime(date('Y-m-d')); // 维护一个键名列表 if (!$redis->exists($key)) { $listlogkey = 'log:key'; $redis->rpush($listlogkey, $key); } // 日志信息存放到redis中 $redis->rpush($key, $log);
The scheduled task code is as follows:
$lastMonth = strtotime("-30 day"); while ($logkey = $redis->lpop('log:key')) { $logTime = explode(':', $logkey)[1]; if ($logTime < $lastMonth) { // 从日志列表里去日志信息,一次取50条 for ($start = 0, $end = 49;true;$start +=50, $end+=50) { $logs = $redis->lrange($logkey, $start, $end); if (!$logs) break; // 将日志信息解压缩,然后追加写入文本文件中 …… // 删除该日志列表 $redis->del($logkey); } } else { // 一个月之内的,重新push到左侧 $redis->lpush('log:key', $logkey); exit; } }
There are a few points to note here. If the persistent log fails, or it is a log within the past month, you need to Re-push the log list key name from the left. In addition, when fetching logs from the log list, do not fetch them all at once, as this may easily lead to redis blocking. Each time, take a certain number (such as 50) and take them out in a loop.
Storing popular news IDs
I won’t post the code here, but mainly talk about the ideas. I used to create a system with a menu function, including today's hottest, hottest week, and hottest in January. At that time, our website had quite a lot of traffic, but within a few days, the website went down. The reason is that mysql's slow query problem. Because this piece of SQL includes grouping, COUNT(), conditional judgment, etc.
Let me tell you about our solution: write a mysql stored procedure and call the stored procedure regularly. The function of this stored procedure is to filter out the most popular articles today, this week, and January, take 100 article IDs respectively, and store their article IDs in the redis queue. For the most popular articles, we only display the top 100. In this way, our system will have no slow queries.
The above is the detailed content of Redis stores logs and popular articles. 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
