How to set the redis expiration policy

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 the delete expired key only when key is read or written. It can be set through lazyfree-lazy-eviction, lazyfree-lazy-expire, lazyfree-lazy-user-del parameters.

Redis Expiration Policy Settings

There are two main data expiration strategies in Redis:

• Periodic deletion: The system scans all keys regularly and deletes expired keys.
• Lazy Deletion: Expired keys are checked and deleted only when keys are read or written.

Expiration policy settings

1. Delete regularly

 <code class="shell">CONFIG SET expired-time-cap-remove-count 100000 # 每次扫描删除的最大键数量CONFIG SET expired-time-cap-remove-delay 5 # 删除操作的延迟时间（秒）</code>

2. Lazy deletion

 <code class="shell">CONFIG SET lazyfree-lazy-eviction true # 启用惰性删除CONFIG SET lazyfree-lazy-expire false # 失效后立即开始删除操作CONFIG SET lazyfree-lazy-user-del true # 通过DEL 命令删除的键立即删除</code>

Parameter description

• expired-time-cap-remove-count: The maximum number of keys deleted per scan.
• expired-time-cap-remove-delay: Delete operation delay time to reduce server load.
• lazyfree-lazy-eviction: Enable lazy deletion.
• lazyfree-lazy-expire: Start the deletion operation immediately after it expires.
• lazyfree-lazy-user-del: The keys deleted by the DEL command are deleted immediately.

Select a policy

The regular deletion strategy is suitable for scenarios with large data volumes. Expired keys can be deleted regularly to avoid memory waste. The lazy deletion strategy is suitable for scenarios with small data volume or high performance requirements, which can reduce the overhead of server scanning and deletion operations.

The above is the detailed content of How to set the redis expiration policy. For more information, please follow other related articles on the PHP Chinese website!