CAR is billed by cloud application rendering concurrency. In CAR, a concurrency represents the collection of virtual computing resources, including CPU, bandwidth, disk, and GPU, required for one user to render your application content. Each concurrency supports access to your application by only one user at a time.
Billing items - CAR concurrency
A concurrency represents the collection of virtual computing resources, including CPU, bandwidth, disk, and GPU, required for one user to render your application content. Each concurrency supports access to your application by only one user at a time.
CAR supports hybrid scheduling of concurrencies in x86 and ARM architectures.
x86 concurrency: Has a high performance with the computing power of a desktop graphics card and is generally suitable for PC desktop applications.
ARM concurrency (Whitelist Activation): Has a high cost performance and low application adaptation costs and is generally suitable for Android applications.
|
x86 GPU | S - For rendering small applications | Small desktop applications |
| M - For rendering medium-sized applications | Medium-sized desktop applications |
| L - For rendering large applications | Large desktop applications |
x86 CPU | 4-core CPU type concurrency | Desktop or web applications without GPU requirements |
| 8-core CPU type concurrency |
|
| 16-core CPU type concurrency |
|
ARM （Whitelist Activation） | Enhanced cloud ARM concurrency | Android applications |
| Ultimate cloud ARM concurrency |
|
Note：
In CAR, a concurrency is a virtual resource that supports one user to access your cloud application. Concurrency scales differ in their architecture and configuration, but they do not determine the number of concurrent users that can access an application. For example:
Suppose you have a large-scale virtual concert application. To guarantee there are enough computing resources to render your application, you can choose concurrency scale L with a high GPU performance. If you want to sustain 1,000 users accessing your cloud environment at the same time during peak hours, you can purchase 1,000 monthly or daily subscribed L concurrencies and make additional users queue up to wait for concurrencies to become available. To learn more about queueing, see Queue Feature. For more information on CAR concurrency scales, see Billing. Billing mode
CAR concurrency packs are prepaid in a monthly or daily subscribed manner or purchased as resource packages. For more information, see Billing. Note：
If you terminate and return the monthly subscription package for a CRA concurrency, you will be billed at the rate for a daily subscription package for the resources that have been used. The remaining prepaid amount will be refunded to you.
A prepaid resource package is billed hourly. It takes effect upon purchase and is valid for six months, after which unused resources will expire and cannot be refunded or renewed. You can return an unused resource package that is within the validity period for a full refund. Partially used resource packages are not eligible for refund or return.
Value-Added Feature Billing Item: Cloud-Based Push Streaming
CAR supports additional push streaming of the cloud-rendered images. There are two methods of push streaming: (1) Streaming to cloud live broadcasting by binding a cloud live broadcast domain; (2) Transmitting the target streaming address to stream the image to the specified address. The cloud-based push streaming feature needs to be enabled in the console before it can be called through the API. For detailed billing information, please refer to the Billing. Value-Added Feature Billing: Multiplayer Interaction
In the multiplayer interaction mode, the room is created by a CAR player (i.e., the room owner), and then other players (i.e., interactive audience) can join the same room via the room owner's UserId. In the same room, all users can see the same cloud-rendered scene through a cloud rendering connection. To use the multiplayer interaction feature, it must be actively enabled in the console, and then it can be called via API. For detailed billing information regarding this value-added feature, please refer to billing.