In CAR, concurrencies are scheduled for applications based on which project the application is associated with. After you upload an application, you need to associate it with a project. Then the application can use the concurrency packs (computing resources) that are bound to that project.
Directions
1. In the CAR console, click Projects on the left sidebar and click Create project.
2. On the Create project page, set the following configuration items and click Create.
Basic settings
Configuration Items
Description
Basic settings
Project name
A custom project name. It can contain up to 16 letters, digits, or hyphens (-).
Project type
Single-application: The project is associated with only one application, and all concurrency packs bound to the project are dedicated to that one application. The prelaunch feature can be enabled.
Multi-application: Concurrency packs that are bound to the project are shared by all applications within the project, but the prelaunch feature cannot be enabled.
Select an application to be associated with the project.
Concurrency Scale
Select the concurrency scale for the project.
Project types
CAR supports two types of projects:
Single-application project: The project is associated with only one application, and all concurrency packs bound to the project are dedicated to that one application. This guarantees the availability of resources, and you can enable the prelaunch feature to quickly load the application when a user connects to it.
Multi-application project: Like a resource pool, concurrency packs bound to the project can be shared by all applications. When an end user makes a request, idle concurrencies can be scheduled from the pool in real time. For more information, see How to Implement Concurrency Sharing Through Multi-Application Project.
Project Type
Description
Main Strengths
Use Case
Single-application
The project is associated with only one application, and concurrency packs bound to the project can be used only by that application.
When you call the ApplyConcurrent API to request a concurrency, you need to pass in the ProjectId parameter.
You can enable the prelaunch feature to quickly load the application when a user connects to it.
A virtual exhibition application requires at least 100 concurrencies and uses the prelaunch feature to allow users to quickly access the application without waiting for it to load.
Multi-application
Concurrency packs that are bound to the project are shared by all the applications under the project, but the prelaunch feature cannot be enabled.
When you call the ApplyConcurrent API to request a concurrency, you need to pass in both the ProjectId and ApplicationId parameters.
Multiple applications can share concurrencies to reduce costs.
Multiple exhibition applications which are independent of each other need to share the concurrency pool, so that each application can get idle concurrencies from the pool as needed when there are user access requests.
Note:
To maintain a balance between user experience and cost optimization, you can create a single-application project and a multi-application project and use them together:
When there are user requests, you can first schedule the concurrencies in the single-application project. If prelaunch is enabled for the project, users can quickly use the application without waiting for it to load.
When available concurrencies in the single-application project become insufficient (ApplyConcurrent() returns a prompt indicating that there are no idle concurrencies), you can then schedule concurrencies in the multi-application project.
Projects allow customization of parameters such as frame rate, bitrate range, default cloud desktop resolution, application startup parameters, pre-launch, wait time for reconnection, etc. You can adjust these parameters according to your needs.
You can create different projects to set different parameters for the same application. For example, you can create two projects for the same application, one project with S-type concurrency, 30FPS, and 3-6Mbps bitrate range, and the other project with L-type concurrency, 60FPS, and 5-8Mbps bitrate range. This way, you can provide the first project to ordinary users and the second project to VIP users.
Configuration Items
Description
Advanced settings
Frame rate
Dynamic frame rate (recommended): adjusts the actual encoding frame rate based on the actual rendering frame rate of the cloud application.
Specified frame rate: supports options of 30FPS and 60FPS. If you have other requirements, please contact your Tencent Cloud sales rep for assistance.
Bitrate range
The bitrate range is related to the concurrency scale, and the default values are as follows.
S - For rendering small applications: 3-6Mbps
M - For rendering medium-sized applications: 4-8Mbps
L - For rendering large applications: 5-8Mbps
XL - For rendering extra large applications: 7-10Mbps
It is not supported to exceed the maximum bit rate value specified by the concurrency scale. If you have special requirements, please contact your Tencent Cloud sales rep for assistance.
Default resolution
That is the default desktop resolution of the cloud concurrency instance, which can be set up to 3000 x 3000. If you have higher resolution requirements, please contact your Tencent Cloud sales rep for assistance. If you need to adapt to the resolution of different terminal devices, please refer to the adaptive resolution documentation.
Startup parameter
The startup parameters configured in the project will override the startup parameters configured in the application. If not filled in, the startup parameters filled in the application configuration will be used by default.
App prelaunch
This feature allows you to open the application in advance in the cloud concurrency instance (without any additional fees) and complete the loading process before the user uses it, achieving instant application startup. This feature is only available for single-application type applications and is not supported for multi-application type projects.
Wait time for prelaunch
Cloud disks have slower IO speed compared to local disks, causing slower startup of applications in concurrencies. To ensure a smoother user experience, it's recommended to enable the prelaunch function and set an appropriate wait time to allow prelaunch to complete before connecting the next user. For instance, if the app takes 5 seconds to open locally, it is recommended to set the waiting time to 30 seconds.
Waiting time for reconnection
To prevent users from accidentally exiting the application, a certain duration is reserved for users to re-enter the application. You can also maintain user connection status based on heartbeats in the backend, and release the concurrency directly by calling the DestroySession API (without waiting for reconnection).
Yes
No
Was this page helpful?