This topic describes the resource limits in Function Compute.
Resource limits for services
|Functions per service||50|
|Triggers per function||10|
Resource limits for function execution
|Item||Upper limit (elastic instance)||Upper limit (performance instance)|
|Temporary disk space (the /tmp directory)||512 MB||10 GB|
|Total processes and threads||1024||1024|
|Memory required to execute a function||3 GB||16 GB|
|Duration for which a function is executed||900s||7200s|
|Duration for which an initializer function is executed||300s||300s|
|Response payload size of synchronous invocation||6 MB||6 MB|
|Request payload size of asynchronous invocation||128 KB||128 KB|
|Deployment package size (ZIP or JAR file)||100 MB||500 MB|
|Source code size||500 MB||10 GB|
Resource limits per region per account
|Total size of uploaded deployment packages||100 GB|
Note If you require more on-demand instances, submit a ticket.
|Single instance concurrency||1–100|
Limits on accessing other Alibaba Cloud services or resources
Assume that the feature of accessing resources in a virtual private cloud (VPC) is enabled for Function Compute in your region. The following network limits exist when you invoke functions to access other Alibaba Cloud services or resources:
- You cannot access the resources on an Elastic Compute Service (ECS) instance by using its internal IP address on the classic network. The resources include web services and file systems. You must use its public IP address to access the resources or migrate the resources to a VPC.
- You cannot access an ApsaraDB RDS instance by using its internal IP address on the classic network. You must use its public IP address or migrate the RDS instance to a VPC.
- You cannot access an Alibaba Cloud service by using its internal endpoint. You must use a VPC endpoint or public endpoint provided by this service.