This topic describes the billing components and rules for pay-as-you-go Global Accelerator instances.
The first time you use a pay-as-you-go GA instance, you must Activate the Service.
If your trial usage exceeds the free quota, the system automatically deducts fees from your account balance based on pay-as-you-go rates. Log on to the savings plan to check your balance. The service stops if your account has an overdue payment.
Billing rules
Pay-as-you-go is a postpaid model. The billing rules for pay-as-you-go Global Accelerator instances are as follows:
|
Instance type |
Billing items |
Billing cycle |
|
Standard Global Accelerator instance |
The billing items for standard Global Accelerator instances include the following: |
All billing items for pay-as-you-go Global Accelerator instances are billed hourly. If your usage in a billing cycle is less than one hour, you are charged for one full hour. Bills are typically generated within one hour after the end of the current billing cycle. The exact billing time depends on the system. |
|
Basic Global Accelerator instance |
The billing items for basic Global Accelerator instances include the following: |
- Use the Global Accelerator (pay-as-you-go) CU calculator to estimate instance and CU fees for pay-as-you-go standard Global Accelerator instances.
-
You can purchase GA resource plans to offset the compute unit (CU) fees and instance fees of pay-as-you-go Global Accelerator instances. Resource plans are more cost-effective than the pay-as-you-go billing method. For more information, see GA resource plans.
Instance fee
Fees explained
You are charged instance fees for occupying an instance based on the unit price and usage duration of the instance. Both Standard Global Accelerator instances and Basic Global Accelerator instances incur instance fees.
Billing for an instance starts by the hour as soon as the Global Accelerator instance is created. Billing continues regardless of whether the instance is fully configured or actively used. Even if the instance remains unconfigured, you are still billed. Release the instance promptly if you no longer need it to stop billing.
Billing formula
Instance fee = Instance unit price (USD/hour) × Billing duration (hours)
Instance unit price
The prices in the following table are catalog prices. Actual prices appear on your bill. For details on how to view your bill, see View bills and usage details.
|
Billing item |
Instance unit price (USD/hour) |
|
Global Accelerator instance |
0.02 |
CU fee
Fees explained
The Capacity Unit (CU) is the smallest billing unit used to measure resource consumption by Global Accelerator. CU fees are based on hourly CU usage derived from performance metrics and the billing duration.
Billing formula
Hourly CU fee = CU unit price (USD/CU/hour) × Hourly CU count
Hourly CU count = MAX {New Connections CU count, Concurrent Connections CU count, Data Processing CU count, Rule Evaluation CU count}
The hourly CU count is converted from performance metrics, and you pay based on the metric with the highest CU usage. The total CU fee for a single Global Accelerator instance equals the sum of CU fees across all its listeners. For details on calculating hourly CU counts from performance metrics, see CU usage definition.
Currently, Global Accelerator only charges for Data Processing CU count. Fees for New Connections CU count, Concurrent Connections CU count, and Rule Evaluation CU count are not currently applied.
CU unit price
For any given hour, after converting each performance metric of a Global Accelerator instance into CUs, the system calculates the actual CU consumption for that hour with a precision of up to 0.000001 CU. For example, if you consume 0.1 CU in an hour, your CU fee for that hour is 0.1 × 0.057 = 0.0057 USD.
The prices in the following table are catalog prices. Actual prices appear on your bill. For details on how to view your bill, see View bills and usage details.
|
Billing item |
CU unit price ( USD/CU/hour) |
|
Capacity Unit (CU) |
0.057 |
CU usage definition
The performance metrics included in a single CU depend on the protocol used by the Global Accelerator listener.
|
Traffic type |
Metric name |
Description |
Measurement interval |
CU coefficient |
Hourly CU count calculation |
|
TCP traffic |
New Connections |
Number of new TCP connections processed per second. |
Second |
800 |
During a billing cycle, the system records all new TCP connections per second and divides the maximum value by the CU coefficient to get the New Connections CU count. The formula is: CU count = Maximum New Connections ÷ CU coefficient |
|
Concurrent Connections |
Number of concurrent TCP connections per minute. |
Minute |
100,000 |
During a billing cycle, the system records concurrent TCP connections per minute and divides the maximum value by the CU coefficient to get the Concurrent Connections CU count. The formula is: CU count = Maximum Concurrent Connections ÷ CU coefficient |
|
|
Processing data volume |
Volume of TCP request and response data processed by Global Accelerator, measured in GB. |
Hour |
1 GB |
During a billing cycle, the system records the total TCP request and response data volume and divides it by the CU coefficient to get the Data Processing CU count. The formula is: CU count = Total Data Processing ÷ CU coefficient |
|
|
UDP traffic |
New Connections |
Number of new UDP connections processed per second. |
Second |
400 |
During a billing cycle, the system records all new UDP connections per second and divides the maximum value by the CU coefficient to get the New Connections CU count. The formula is: CU count = Maximum New Connections ÷ CU coefficient |
|
Concurrent Connections |
Number of concurrent UDP connections per minute. |
Minute |
50,000 |
During a billing cycle, the system records concurrent UDP connections per minute and divides the maximum value by the CU coefficient to get the Concurrent Connections CU count. The formula is: CU count = Maximum Concurrent Connections ÷ CU coefficient |
|
|
Processing data volume |
Volume of UDP request and response data processed by Global Accelerator, measured in GB. |
Hour |
1 GB |
During a billing cycle, the system records the total UDP request and response data volume and divides it by the CU coefficient to get the Data Processing CU count. The formula is: CU count = Total Data Processing ÷ CU coefficient |
|
|
HTTP(S) traffic |
New Connections |
Number of new HTTP(S) connections processed per second. |
Second |
25 |
During a billing cycle, the system records all new HTTP(S) connections per second and divides the maximum value by the CU coefficient to get the New Connections CU count. The formula is: CU count = Maximum New Connections ÷ CU coefficient |
|
Concurrent Connections |
Number of concurrent HTTP(S) connections per minute. |
Minute |
3,000 |
During a billing cycle, the system records concurrent HTTP(S) connections per minute and divides the maximum value by the CU coefficient to get the Concurrent Connections CU count. The formula is: CU count = Maximum Concurrent Connections ÷ CU coefficient |
|
|
Processed data volume |
Volume of HTTP(S) request and response data processed by Global Accelerator, measured in GB. |
Hour |
1 GB |
During a billing cycle, the system records the total HTTP(S) request and response data volume and divides it by the CU coefficient to get the Data Processing CU count. The formula is: CU count = Total Data Processing ÷ CU coefficient |
|
|
Rule Evaluation |
Product of the total number of rules processed by Global Accelerator and queries per second (QPS).
Important
Rule Evaluation is affected by two metrics: forwarding rules and extended certificates. Both have a free quota of 25. Only the portions exceeding the free quota are billed. Metrics within the free quota are not counted. |
None |
1,000 |
During a billing cycle, the system records the total number of forwarding rules and QPS, then uses the maximum QPS to calculate Rule Evaluation. Dividing Rule Evaluation by the CU coefficient gives the Rule Evaluation CU count. The formula is: CU count = Rule Evaluation ÷ CU coefficient |
CU billing example
At 08:10:00 on June 2, 2023, one medium pay-as-you-go Global Accelerator instance was created, and a TCP listener was configured for this instance. The instance was released at 08:50:00 on June 2, 2023. During the period from 08:10:00 to 08:50:00 (one billing cycle), the sample data for the maximum number of new connections, maximum number of concurrent connections, and data transfer volume of this Global Accelerator instance are shown in the following table.
|
Metric name |
TCP |
CU count |
|
New Connections (per second) |
Maximum new TCP connections in the hour: 4,000 |
CU count for the hour = 4,000 ÷ 800 = 5 |
|
Concurrent Connections (per minute) |
Maximum concurrent TCP connections in the hour: 720,000 |
CU count for the hour = 720,000 ÷ 100,000 = 7.2 |
|
Data Processing (per hour) |
Total TCP request and response data processed in the hour: 10 GB |
CU count for the hour = 10 ÷ 1 = 10 |
In this example, the CU fee for the TCP listener in that hour = 0.057 USD/CU × MAX {5, 7.2, 10} = 0.057 USD/CU × 10 = 0.57 USD
Estimate CU consumption
Use the Global Accelerator (pay-as-you-go) CU calculator to estimate CU consumption.
Traffic fee (billed through CDT)
When using a pay-as-you-go Global Accelerator instance with bandwidth billing set to Pay-By-Data-Transfer, you incur traffic fees in addition to instance and CU fees. Traffic fees are billed and invoiced through CDT. For traffic billing rules, see Traffic fee.