tencent cloud

Tencent Cloud Observability Platform

Release Notes and Announcements
Release Notes
Product Introduction
Overview
Strengths
Basic Features
Basic Concepts
Use Cases
Use Limits
Purchase Guide
Tencent Cloud Product Monitoring
Application Performance Management
Mobile App Performance Monitoring
Real User Monitoring
Cloud Automated Testing
Prometheus Monitoring
Grafana
EventBridge
PTS
Quick Start
Monitoring Overview
Instance Group
Tencent Cloud Product Monitoring
Application Performance Management
Real User Monitoring
Cloud Automated Testing
Performance Testing Service
Prometheus Getting Started
Grafana
Dashboard Creation
EventBridge
Alarm Service
Cloud Product Monitoring
Tencent Cloud Service Metrics
Operation Guide
CVM Agents
Cloud Product Monitoring Integration with Grafana
Troubleshooting
Practical Tutorial
Application Performance Management
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Parameter Information
FAQs
Mobile App Performance Monitoring
Overview
Operation Guide
Access Guide
Practical Tutorial
Tencent Cloud Real User Monitoring
Product Introduction
Operation Guide
Connection Guide
FAQs
Cloud Automated Testing
Product Introduction
Operation Guide
FAQs
Performance Testing Service
Overview
Operation Guide
Practice Tutorial
JavaScript API List
FAQs
Prometheus Monitoring
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Terraform
FAQs
Grafana
Product Introduction
Operation Guide
Guide on Grafana Common Features
FAQs
Dashboard
Overview
Operation Guide
Alarm Management
Console Operation Guide
Troubleshooting
FAQs
EventBridge
Product Introduction
Operation Guide
Practical Tutorial
FAQs
Report Management
FAQs
General
Alarm Service
Concepts
Monitoring Charts
CVM Agents
Dynamic Alarm Threshold
CM Connection to Grafana
Documentation Guide
Related Agreements
Application Performance Management Service Level Agreement
APM Privacy Policy
APM Data Processing And Security Agreement
RUM Service Level Agreement
Mobile Performance Monitoring Service Level Agreement
Cloud Automated Testing Service Level Agreement
Prometheus Service Level Agreement
TCMG Service Level Agreements
PTS Service Level Agreement
PTS Use Limits
Cloud Monitor Service Level Agreement
API Documentation
History
Introduction
API Category
Making API Requests
Monitoring Data Query APIs
Alarm APIs
Legacy Alert APIs
Notification Template APIs
TMP APIs
Grafana Service APIs
Event Center APIs
TencentCloud Managed Service for Prometheus APIs
Monitoring APIs
Data Types
Error Codes
Glossary

Pay-as-You-Go (postpaid)

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-11-24 16:29:23
Performance Testing Service (PTS) supports pay-as-you-go (postpaid), which is billed based on the actual usage of performance testing. Bills are generated in each billing cycle and the corresponding fees are deducted from the account. You can refer to the following to estimate the costs of PTS.

Billing Description

Every time a testing scenario execution task completes, the fees are calculated based on the consumed VUM. The number of resources and the duration used for performance testing affect the VUM consumption. The calculation is as follows:
VUM consumption = Number of performance testing resources × 500 (concurrency) × Duration (number of minutes)
One performance testing resource = 500 VUs (less than 500 VUs is calculated as 500 VUs)
Notes:
The resources used by PTS are split based on 500 VUs, the minimum measurement unit, which is allocated to the users as a "performance testing resource" (or understood as a virtual load generator with the capability of 500 concurrency). Therefore, during calculation of VUM, VUs are always an integer multiple of 500.
The duration of performance testing is measured in unit of a minute. If it is less than 1 minute, seconds are converted to minutes to calculate the duration (1 minute = 60 seconds, and 15 seconds = 15/60 = 0.25 minutes).
For example, if the total duration of a performance testing scenario is 7 minutes and 45 seconds, the 45 seconds will be converted to 0.75 minutes (45/60). Therefore, the total billing duration for this testing is 7.75 minutes.

Calculation Formula

Total costs = VUM consumption × Unit price

Product Billing

Billing Item
Unit Price (USD)
VUM consumption
0.0008 USD/VUM

Billing Instructions

Pay-as-you-go billing mode has the following specification limits.
Specification Name
Limit
Maximum VU
50,000
Maximum RPS
400 thousand
Tasks running concurrently
10
Total size of parameter files
500 MB
Maximum size of script file
100 KB

Billing Cycle

PTS adopts pay-as-you-go mode, billed daily. At a fixed time on the previous day of the settlement day, the system calculates the charges for the VUM consumption, generates a bill, and automatically deducts the fees from the account balance. The actual billing at settlement time shall prevail.

Viewing Pay-as-You-Go Bills

PTS adopts the pay-as-you-go mode, which is billed daily. You can check the bill for the VUM consumption generated for the previous day.
1. Go to Billing Center, select Bills > View Bills.
2. On the Bill Details tab, set the following filters for search: select Product Name as Performance Testing Service and Subproduct Name as PTS Pay-As-You-Go. Then press Enter to execute the search. You can check your pay-as-you-go bill in the billing list.

Billing Example

Suppose you have used 5 resources for a performance testing, with a total testing duration of 6 minutes:
VUM consumption = 5 × 500 × 6 = 15000 VUM
Total costs = 15000 VUM × 0.0008 USD/VUM = 12 USD

도움말 및 지원

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

피드백