Skip to main content

Usage Limits

Pay-as-You-Go Usage

For the CloudRun service, since it currently uses a pay-as-you-go billing model, the related CPU and MEM usage is not included in the CloudBase environment package. Therefore, when using the CloudRun service, you need to enable the over-limit pay-as-you-go service for the environment, so that CloudRun can be metered and billed in pay-as-you-go mode. If you disable the over-limit pay-as-you-go for the environment, it will result in service suspension.

Environment Isolation

All resources between multiple environments in Cloud Development are mutually isolated.

Services within the CloudRun environment can call each other via the internal network.

Resources between different environments can only be accessed via public network.

Service and Instance Quotas

You can create up to 15 services in a single CloudBase environment.

In a single CloudBase environment, you can run up to 28 instances. This count includes instances started by all services. Once the maximum is reached, no more instances can be automatically scaled out.

Currently, if you need to increase the limits, you can apply by submitting a ticket.

QPS Limits

All services of CloudRun in a CloudBase environment are subject to the total QPS (queries per second) limit at the environment level. The specific QPS limit for an environment can be queried in the package specifications.

CloudRun Request Timeout: 60s

CloudRun Request Body Size: 20M