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

Billing Overview

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-17 16:36:35

Overview

Tencent Cloud Distributed Cache offers two billing modes: yearly/monthly subscription and pay-as-you-go. Users can select the appropriate billing mode based on business needs, cost budgets, and resource usage patterns. This document details the features, rules, and selection recommendations for both billing modes.

Billing Modes

Comparison Item
Yearly/Monthly Subscription
Pay-as-You-Go
Billing method
Prepaid: Pay the full fee for the selected duration (such as month and year) in one go.
Subscription period: Monthly/Yearly purchase. The minimum subscription period is 1 month, and the maximum is 5 years.
Product pricing: Priced on a monthly basis. The longer the subscription period, the more pricing discounts you get. For specific pricing, see Pricing Center.
Postpaid: Billed hourly. Pay after usage.
Settlement cycle: Upon activation, one hour's fee will be frozen in your cloud account. At the top of every hour (UTC+8), the fee for the previous hour will be settled automatically.
Product pricing: Tiered pricing based on usage duration. The hourly unit price decreases progressively with each tier. For specific pricing, see Pricing Center.
Tier 1: 0 days < Duration ≤ 4 days, Hourly price = Monthly price/30/24 x 2.
Tier 2: 4 days < Duration ≤ 15 days, Hourly price = Monthly price/30/24 x 1.5.
Tier 3: Duration > 15 days, Hourly price = Monthly price/30/24.
Note:
After instance scale-out, scale-in, or isolation, the pricing calculation restarts from Tier 1.
The price of pay-as-you-go tier 3 is basically the same as that of yearly/monthly subscription.
Key rules
Renewal: Instances can be renewed manually or automatically upon expiration. For specific renewal operations, see Renewal.
Return: Instances can be unsubscribed at any time, with remaining fees settled according to applicable rules. For specific refund policies, see Refund.
Overdue Payments: If an instance expires without renewal and remains in arrears beyond the grace period and retention period, the instance will be released. For details on how to deal with overdue payments, see Overdue Payments.

Termination: Instances can be terminated at any time, with fees settled per second based on usage.
Overdue Payments: If the account balance is insufficient, the instance will be released after overdue payments exceed the grace period and retention period.
Core strengths
Lower unit prices, and more favorable long-term usage costs.
Highly flexible, with on-demand resource purchase and release to adapt to business fluctuations.
Application scenarios
Production environments or core business that is stable and operates over the long term.
Business with significant traffic fluctuation and temporary needs (such as development and testing and promotional campaigns).

Billable Items

Billing basis: Billing is based on the instance's memory capacity (such as 1 GB, 4 GB, 16 GB, 64 GB, and so on).
Cost coverage: The cost covers the consolidated costs of the following core resources.
Computing resources: CPU resources that support the operation of the Tencent Cloud Distributed Cache service.
Memory resources: Data storage space.
Network and maintenance: Private network access for instances, and underlying platform maintenance.
Pricing policy: Linear pricing, where cost is proportional to memory capacity. The larger the capacity, the higher the cost.
Regional variations: Infrastructure costs differ across regions, and pricing varies accordingly.
Architectural differences: Pricing varies across product series based on performance, features, and complexity.

Billing Formula

Standard Architecture

Cost = Per-node memory x Per-node pricing x Number of nodes
Note:
The standard architecture supports primary-secondary replication mode, such as a 1-master-1-replica architecture that includes 2 nodes. During billing, the total memory capacity of all nodes must be accounted for.
Assume that you select the standard architecture and 1-master-1-replica mode, with per-node memory of 8 GB and per-node pricing of 5.30 USD/GB/month: Yearly/monthly subscription cost calculation: 8 GB x 5.30 USD/GB/month x 2 nodes = 84.8 USD/month.

Cluster Architecture

Cost = Per-shard memory x Per-shard pricing x Number of nodes x Number of shards
Note:
The cluster architecture is composed of multiple shards, with each shard supporting primary-secondary replication. During billing, the total memory capacity of all shards and their nodes must be accounted for.
Assume that you select the cluster architecture, 3 shards, with each shard in 1-master-1-replica mode, per-shard memory of 8 GB, per-node pricing of 5.86 USD/GB/month:
Yearly/monthly subscription cost calculation: 8 GB x 5.86 USD/GB/month x 2 nodes x 3 shards = 281.28 USD/month.

Cost Estimation

To estimate costs, first determine the product series and billing mode based on your business scenarios., Then, select the required memory specifications, and query the detailed pricing details for the target region.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백