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
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

Specifications and Performance

PDF
Focus Mode
Font Size
Last updated: 2026-03-17 16:36:35

Specifications

Note:
As a trial version, the 256 MB specification on v4.0 or v5.0 is only suitable for product verification in testing environments. We don't recommend that you use it in production environments. It is available only in the following AZs:
Guangzhou (Zones 6 and 7), Shanghai (Zones 2, 3, 4 and 5), Beijing (Zones 1, 2, 3, 4, 5, 6, and 7), and Shenzhen Finance (Zones 1, 2, and 3). Other 1 GB and above specifications can be smoothly downgraded to the 256 MB specification.
Feature
Standard Architecture
Cluster Architecture
Memory specifications
256MB - 64GB
Single shard: 1 GB to 64 GB
Number of replicas
1 - 5
1 - 5
Number of shards
N/A
1, 3, 5, 8, 12, 16, 24, 32, 40, 48, 64, 80, 96, 128, and 256
QPS
80,000–100,000
80000 to 100000 per shard
Maximum number of connections
10000 by default, adjustable up to 40000
10000 per shard by default, adjustable up to 40000
Traffic limit
528MB/s - 608MB/s
288MB/s - 72GB/s
Multiple databases
Supported
Supported
Mget and Mset
Supported
Supported
lua
Supported
Supported (cross-slot access not supported)
Horizontal scale-out
Not supported
Supported
Replica scale-out
Supported
Supported
Read-write separation
Supported
Supported
Support for GEO
Supported
Supported

Description of the CPU core quantity

To ensure the stable operations of the system, each node is assigned with 2-core CPU, one of which is used to process the backend tasks.

Number of Connections and Traffic

Distributed Cache offers tiered options with customizable core performance metrics including storage capacity, connections, QPS, and bandwidth.
Content Capacity (GB)
Maximum number of connections
Maximum throughput (MB/s)
0.25
3,000
10
1
40,000
16
2
40,000
24
4
40,000
24
8
40,000
24
12
40,000
32
16
40,000
32
20
40,000
48
24
40,000
48
32
40,000
48
40
40,000
64
48
40,000
64
64
40,000
64
The number of connections in the Cluster Edition = Shard connections * Number of shards. For the throughput of the Cluster Edition, see Bandwidth Adjustment.
Note:
After scaling, legacy instances capable of up to 9,000 connections will be capable of 10,000 connections.

Performance Data

Performance references

As the execution time of commands varies, and database operation commands differ across business scenarios in production environments, the corresponding performance will also vary. The test data provided in this document is a reference value obtained under specified parameters and shall only serve as a reference. Actual performance needs to be verified through tests based on actual business scenarios.

Single-node test performance

Instance Specifications
Connections
QPS
standard architecture 8GB
10,000
80,000–100,000
cluster architecture 8GB (single shard)
10,000
80,000–100,000

Cluster architecture test performance

Memory Edition (Cluster Architecture) performance = Memory Edition (Standard Architecture) performance * number of shards

Test method

Test environment

Test Client CVM Instances
CVM Cores
CVM Memory
Region
Instance Size
3
2
8 GB
Guangzhou Zone 2
Memory Edition (Standard Architecture) 8 GB

Test parameters

redis-benchmark -h 10.66.187.x -p 6379 -a crs-1znib6aw:chen2016 -t set -c 3500 -d 128 -n 25000000 -r 5000000
redis-benchmark -h 10.66.187.x -p 6379 -a crs-1z5536aw:chen2016 -t set -c 3500 -d 128 -n 25000000 -r 5000000
redis-benchmark -h 10.66.187.x -p 6379 -a crs-090rjlih:1234567 -t set -c 3500 -d 128 -n 25000000 -r 5000000

QPS calculation

Sum of the QPS values of three pressure test clients (tested by redis-benchmark).

Help and Support

Was this page helpful?

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

Feedback