This topic describes the billing rules and billable items of pay-as-you-go Global Accelerator (GA) instances.
The first time you use a pay-as-you-go GA instance, go to the pay-as-you-go GA activation page and activate GA as prompted.
Pay-as-you-go GA instances use the pay-by-data-transfer metering method. You do not need to associate a basic bandwidth plan with pay-as-you-go GA instances. The billing of data transfer over the GA network is managed by Cloud Data Transfer (CDT). For more information, see Pay-by-data-transfer.
Billing rules
The pay-as-you-go billing method allows you to use resources before you pay for the resources. The following table describes the billing rules for GA instances.
Instance type | Billable item | Billing cycle |
Standard GA instance | Instance fee and capacity unit (CU) fee | Hours If the usage duration in a billing cycle is less than 1 hour, the usage duration is rounded up to 1 hour. A bill is generated 1 hour after the current billing cycle ends. The system determines the time when bills are issued. |
Basic GA instance | Instance fee |
Instance fee
Description
You are charged an instance fee for a GA instance based on the unit price and usage duration of the instance.
Formula
Instance fee = Instance unit price (USD per hour) × Usage duration (hours)
Unit price
The unit price of instances in this topic is for reference only. You can view the actual unit price on your bills. For information about how to view bills, see View billing details.
The unit price of pay-as-you-go GA instances is USD 0.02 per hour.
CU fee
Description
CUs are the smallest unit that is used to measure the resource consumption of GA instances. CU fees are charged based on the hourly CU consumption and usage duration of performance metrics.
Formula
CU fee per hour = CU unit price (USD per CU) × Number of CUs
Number of CUs consumed per hour = Max {Number of CUs based on new connections per hour, Number of CUs based on concurrent connections per hour, Number of CUs based on data transfer per hour, Number of CUs based on rule evaluations}
The number of CUs that are consumed by a GA instance per hour is the maximum value of the number of CUs required by the performance metrics. The CU fee of a single GA instance is the sum of the CU fees of each listener. For more information about how the number of CUs per hour is calculated for each metric, see CU consumption definition.
You are charged for the number of CUs based only on data transfer on a GA instance. You are not charged for the number of CUs based on new connections, concurrent connections, or rule evaluations.
CU unit price
The instance unit price in this topic is for reference only. The price on your bills shall prevail. For information about how to view bills, see View billing details.
The unit price of CUs is USD 0.057 per CU.
CU consumption definition
The performance metrics of a single CU vary based on the protocol of GA listeners.
Traffic type | Metric | Description | Time unit | CU coefficient | CU calculation |
TCP traffic | Number of new connections (CPS) | The number of new TCP connections that are processed per second. | Seconds | 800 | The system collects all CPS values within a billing cycle and then divides the largest CPS value by the CU coefficient to calculate the number of CUs. The number of CUs based on data transfer is calculated by using the following formula: Number of CUs = Largest CPS value/CU coefficient |
Number of concurrent connections | The number of concurrent TCP connections per minute. | Minutes | 100,000 | The system collects all CONNS values within a billing cycle and then divides the largest CONNS value by the CU coefficient to calculate the number of CUs. The number of CUs is calculated by using the following formula: Number of LCUs = Largest CONNS value/CU coefficient | |
Data transfer | The amount of data transfer over TCP that is processed by GA instances. Unit: GB. | Hours | 1 GB | The system divides the total amount of data transfer over TCP within a billing cycle by the CU coefficient to calculate the number of CUs. The number of CUs is calculated by using the following formula: Number of CUs = Total amount of data transfer/CU coefficient | |
User Datagram Protocol (UDP) listeners | CPS | The number of new UDP connections that are processed per second. | Seconds | 50 | The system collects all CPS values within a billing cycle and then divides the largest CPS value by the CU coefficient to calculate the number of CUs. The number of CUs based on data transfer is calculated by using the following formula: Number of CUs = Largest CPS value/CU coefficient |
CONNS | The number of concurrent UDP connections per minute. | Minutes | 3,000 | The system collects all CONNS values within a billing cycle and then divides the largest CONNS value by the CU coefficient to calculate the number of CUs. The number of CUs is calculated by using the following formula: Number of LCUs = Largest CONNS value/CU coefficient | |
Data transfer | The data transfer over UDP processed by GA instances. Unit: GB. | Hours | 1 GB | The system divides the total amount of data transfer over UDP within a billing cycle by the CU coefficient to calculate the number of CUs. The number of CUs is calculated by using the following formula: Number of CUs = Total amount of data transfer/CU coefficient | |
HTTP and HTTPS listeners | CPS | The number of new HTTP and HTTPS connections processed per second. | Seconds | 25 | The system collects all CPS values within a billing cycle and then divides the largest CPS value by the CU coefficient to calculate the number of CUs. The number of CUs based on data transfer is calculated by using the following formula: Number of CUs = Largest CPS value/CU coefficient |
CONNS | The number of concurrent HTTP and HTTPS connections per minute. | Minutes | 3,000 | The system collects all CONNS values within a billing cycle and then divides the largest CONNS value by the CU coefficient to calculate the number of CUs. The number of CUs is calculated by using the following formula: Number of LCUs = Largest CONNS value/CU coefficient | |
Data transfer | The data transfer over HTTP and HTTPS that is processed by GA instances. Unit: GB. | Hours | 1 GB | The system divides the total amount of data transfer over HTTP and HTTPS within a billing cycle by the CU coefficient to calculate the number of CUs. The number of CUs is calculated by using the following formula: Number of CUs = Total amount of data transfer/CU coefficient | |
Number of rule evaluations | The product of the number of specific items that are processed by a GA instance and the queries per second (QPS). These items include forwarding rules, lines of code in AScript, and additional certificates.
| N/A | 1,000 | The system collects the number of forwarding rules and all QPS values within a billing cycle and uses the highest QPS value to calculate the number of rule evaluations. Then, the system divides the number of rule evaluations by the CU coefficient to calculate the number of CUs. The number of CUs is calculated by using the following formula: Number of CUs = Number of rule evaluations/CU coefficient |
CU billing example
A standard pay-as-you-go GA instance is created at 08:10:00 on June 2, 2023, and a TCP listener is configured for the instance. The instance is released at 08:50:00 on June 2, 2023. The following table lists the largest CPS value, the largest CONNS value, and the total amount of data transfer that is processed by the GA instance within a billing cycle from 08:10:00 to 08:50:00.
Specification | TCP | Number of consumed CUs |
CPS | Up to 4,000 new connections are established per second in the hour. | Number of CUs = 4,000/800 = 5 |
CONNS per minute | Up to 720,000 concurrent connections are established in the hour. | Number of CUs = 720,000/100,000 = 7.2 |
Data transfer per hour | The data transfer over TCP that is processed by a GA instance in the hour is 10 GB. | Number of CUs = 10/1 = 10 |
In this example, the CU fee of the TCP listener for the hour is USD 0.057 × MAX {5, 7.2, 10} = USD 0.057 × 10 = USD 0.57
References
If you use pay-as-you-go GA instances, traffic fees are also incurred besides instance fees and CU fees. For more information, see Pay-by-data-transfer.