- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practice
- Security White Paper
- Development Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- UpgradeDedicatedDBInstance
- ModifyBackupTime
- OpenDBExtranetAccess
- DescribePrice
- ModifyDBInstancesProject
- DescribeFlow
- CloseDBExtranetAccess
- CreateDBInstance
- DescribeBackupTime
- DescribeDBInstances
- InitDBInstances
- ModifyDBInstanceName
- DescribeInstanceNodeInfo
- DescribeDcnDetail
- DestroyHourDBInstance
- CancelDcnJob
- CreateHourDBInstance
- SwitchDBInstanceHA
- IsolateHourDBInstance
- ActivateHourDBInstance
- DestroyDBInstance
- ModifyInstanceVport
- ModifyInstanceVip
- ModifyInstanceNetwork
- IsolateDedicatedDBInstance
- IsolateDBInstance
- TerminateDedicatedDBInstance
- DescribeDBInstanceDetail
- DescribeOrders
- Parameter Management APIs
- Monitoring Management APIs
- Backup and Restoration APIs
- Account APIs
- Security Group APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- General References
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practice
- Security White Paper
- Development Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- UpgradeDedicatedDBInstance
- ModifyBackupTime
- OpenDBExtranetAccess
- DescribePrice
- ModifyDBInstancesProject
- DescribeFlow
- CloseDBExtranetAccess
- CreateDBInstance
- DescribeBackupTime
- DescribeDBInstances
- InitDBInstances
- ModifyDBInstanceName
- DescribeInstanceNodeInfo
- DescribeDcnDetail
- DestroyHourDBInstance
- CancelDcnJob
- CreateHourDBInstance
- SwitchDBInstanceHA
- IsolateHourDBInstance
- ActivateHourDBInstance
- DestroyDBInstance
- ModifyInstanceVport
- ModifyInstanceVip
- ModifyInstanceNetwork
- IsolateDedicatedDBInstance
- IsolateDBInstance
- TerminateDedicatedDBInstance
- DescribeDBInstanceDetail
- DescribeOrders
- Parameter Management APIs
- Monitoring Management APIs
- Backup and Restoration APIs
- Account APIs
- Security Group APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- General References
- Glossary
Billing Modes
TencentDB for MariaDB provides two billing options.
Billing Mode | Payment Mode | Application Scenario |
Monthly subscription | Prepaid. Fees are paid when an instance is created. | Suitable for businesses with long term stable needs as the rates are lower than the pay-as-you-go option. Longer-term purchases results in increased savings. |
Pay-as-you-go | Postpaid. You can request for resources on-demand and will be charged based on the actual usage upon settlement. | Suitable for businesses with fluctuating demands. Instances can be released immediately after use to reduce costs. |
The memory prices for pay-as-you-go adopts a tiered model based on the usage duration.
Usage Duration | Tiered Price |
0 hours < duration ≤ 96 hours | Tier 1 pay-as-you-go price applies |
96 hours < duration ≤ 360 hours | Tier 2 pay-as-you-go price applies |
Duration > 360 hours | Tier 3 pay-as-you-go price applies |
Node Specifications
Configuration Type | Node CPU | Node Memory (GB) |
High IO | 1 | 2 |
High IO | 2 | 4 |
High IO | 4 | 8 |
High IO | 6 | 16 |
High IO | 8 | 32 |
High IO | 16 | 64 |
High IO | 24 | 96 |
High IO | 32 | 128 |
はい
いいえ
この記事はお役に立ちましたか？