tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Database Audit
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

High Memory Utilization

PDF
Focus Mode
Font Size
Last updated: 2026-03-18 17:08:16

Symptom

Symptom 1: You received an alarm about too high memory utilization.
Symptom 2: On the System Monitoring page in the Tencent Cloud Distributed Cache console, you can view that there are sudden rises in Memory Utilization, Key Evictions, and P99 Response Latency.
Symptom 3: The error message command not allowed when used memory > 'maxmemory' was prompted when the program writes data.

Distributed CacheMemory Usage

The data that usually occupies memory in Tencent Cloud Distributed Cache includes the following:
Object memory: User data area, that is, the actual stored value information.
Buffer memory: Including client input and output buffers, and master-replica sync replication buffers.
Note:
When performing Range operations or big keys on the client side, the memory occupied by input buff and output buff will increase, affecting the buffer and even causing OOM.
Memory fragmentation: A large number of update operations, such as append and setrange; a large number of expired keys are deleted, and the released space cannot be effectively used.
Link memory: The memory consumed for creating subprocesses, which is generally relatively small.

Troubleshooting the Issue

No.
Possible Cause
Troubleshooting Method
Solution
1
The increase in the volume of written data leads to an increase in memory usage.
The key is not set in the TTL policy.
1. Log in to the Tencent Cloud Distributed Cache console, click an instance ID, and enter the instance details page.
2. Select the System Monitoring tab to view the corresponding monitoring metrics of the instance, including Memory Utilization, Total Keys, Expired Keys, and Evicted Keys. Then, you can analyze whether the memory utilization is consistent with the fluctuation trend of the number of keys.
If the memory usage is proportional to the total number of keys, the possible causes are as follows.
The memory may be increased due to the normal data written by the business. Evaluate your business needs and expand the Distributed Cache instance in time. For directions, see Changing Instance Specification.
The memory may increase due to the accumulation of keys due to the failure to set a reasonable eviction policy and deletion frequency for expired keys.
The eviction policy setting is unreasonable, which may easily cause invalid keys to occupy too much space. To modify the parameters related to key expiration time, eviction policy, and deletion frequency, reconfigure the maxmemory-policy and hz parameters on the Parameter Settings page in the console. For directions, see Setting Instance Parameters.
If the deletion frequency for expired keys is set too high, that is, if the value of hz increases, more CPU resources will be occupied. The hz value should not be too large. You can adjust it as needed.
2
Input buffer overflow is caused by writing a big key caused the .
Reading large keys, requesting a large number of command returns, or executing monitor commands causes output buffer overflow.
Analyze memory skew issues with the Performance Optimization feature of DBbrain. For more information, see Memory Analysis.
Perform value splitting and optimization for abnormally large keys. For more information, see Hot Key and Big Key.。


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback