Notes and Constraints
Supported Regions
Table 1 lists the supported regions.
Region |
Region ID |
---|---|
AF-Johannesburg |
af-south-1 |
CN-Hong Kong |
ap-southeast-1 |
AP-Bangkok |
ap-southeast-2 |
AP-Singapore |
ap-southeast-3 |
AP-Jakarta |
ap-southeast-4 |
CN East-Shanghai2 |
cn-east-2 |
CN East-Shanghai1 |
cn-east-3 |
CN North-Beijing1 |
cn-north-1 |
CN North-Ulanqab-Auto1 |
cn-north-11 |
CN North-Beijing4 |
cn-north-4 |
CN North-Ulanqab1 |
cn-north-9 |
CN South-Guangzhou |
cn-south-1 |
LA-Mexico City2 |
la-north-2 |
LA-Santiago |
la-south-2 |
ME-Riyadh |
me-east-1 |
LA-Sao Paulo1 |
sa-brazil-1 |
TR-Istanbul |
tr-west-1 |
Account Resource Constraints
The following table provides the quotas for account resources. For details on how to query and modify quotas, see Quotas.
Resource |
Limit |
Adjustable |
---|---|---|
Maximum number of functions that can be created under an account |
400 |
No. |
Maximum number of versions allowed for a function |
20 |
No. |
Maximum number of aliases allowed for a function |
10 |
No. |
Maximum number of triggers (DIS/GeminiDB Mongo/LTS/DDS/Kafka/Timer) allowed for a function version |
10 |
No. |
Size of a code deployment package (in ZIP or JAR format) that can be uploaded to the FunctionGraph console |
40 MB |
No. |
Size of a code deployment package (in ZIP or JAR format) that can be edited inline during function API invocation |
50 MB |
No. |
Size of an original code deployment package allowed during function API invocation |
|
No. |
Maximum size of deployment packages allowed for an account |
10 GB |
No. |
Number of concurrent executions per account |
100 |
Yes |
Maximum number of reserved instances that an account can create |
90 (Number of concurrent executions per account x 90%) |
Yes |
Size of all environment variables of a function |
4096 characters |
No. |
Maximum size of code that can be displayed on the console |
20 MB |
No. |
Function Running Resource Constraints
Resource |
Default |
Adjustable |
---|---|---|
Ephemeral disk space (/tmp space) |
512 MB |
No. |
Number of file descriptors |
1024 |
No. |
Total number of processes and threads |
1024 |
No. |
Maximum execution duration per request |
259,200s |
Yes |
Valid payload size of invocation request body (synchronous invocation) |
6 MB |
No. |
Valid payload size of invocation response body (synchronous invocation) |
6 MB |
No. |
Valid payload size of invocation request body (asynchronous invocation) |
256 KB |
No. |
Size of imported resources |
≤ 50 MB ZIP file |
No. |
Image size per function |
10 GB |
No. |
Size of exported resources |
≤ 50 MB |
No. |
Instances per tenant |
1000 |
Yes |
Max. memory per function |
10 GB |
No. |
Bandwidth |
Unlimited |
- |
Single log size |
Unlimited |
- |
Maximum execution duration of initializer |
259,200s |
Yes |
- Valid payload size of invocation response body (synchronous invocation): The returned character string or the JSON character string of the serialized response body is less than or equal to 6 MB by default. The actual data size varies depending on the backend settings of FunctionGraph. The backend determines the size of the serialized data with a byte-level deviation. The actual valid payload size is 6 MB ± 100 bytes.
- You are not advised to invoke a function whose execution time exceeds 90s on the FunctionGraph console. To invoke such a function, use asynchronous invocation.
- The valid payload size of a request body is 6 MB when a GeminiDB Mongo, DIS, Kafka or DDS trigger is used and is 4 MB when an APIG trigger is used.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot