This topic describes the release notes of Function Compute in 2022 and provides references.
November 2022
Feature | Type | Description | References |
Unit prices | Optimization | Starting from November 3, 2022, the prices of all billable items of Function Compute in all regions are reduced. The billing rules of Function Compute are optimized to help you allocate resources in a more flexible manner and improve resource utilization. The prices for pay-as-you-go resources and resource plans in Function Compute are reduced. Function Compute helps you reduce costs by 12% to 47% even when your daily resource utilization reaches 30%. | |
Instance memory specifications | Optimization | The original memory specifications of instances are changed to vCPU specifications and memory specifications. | |
OSS file system | New | You can configure an Object Storage Service (OSS) file system for a service in Function Compute. After you mount an OSS file system to the service, functions in the service can access specified OSS buckets in the same manner in which functions access a local file system. | |
GPU specifications | Optimization | GPU memory can be set to an integer value from 1 to 16. Unit: GB. |
September 2022
Review type | Type | Description | References |
Advanced features of EventBridge triggers | New | Advanced features such as batch push, retry, and dead-letter queue are supported for EventBridge triggers. | |
Runtime environments
| New | The following runtimes are supported in Function Compute:
| |
Auto scaling of GPU-accelerated instances | New | Function Compute provides the auto scaling feature for provisioned GPU-accelerated instances based on the resource usage of GPU instances, including the streaming multiprocessors (SM), GPU memory, hardware decoder, and hardware encoder usage. | |
gRPC protocol support for HTTP functions | New | HTTP functions can be triggered by gRPC requests. An HTTP function works as a web server and processes gRPC requests. | |
Non-web server mode | New | The non-web server mode is supported in a custom container runtime. If CAPort is not configured, you do not need to define an HTTP server. | |
Custom health check | New | If you select Use Custom Runtime or Use Container Image when you create a function and use your own container image as the function runtime environment, your custom runtime environment may be unstable, which may cause exceptions for function instances. Function Compute supports periodic health checks for function instances to avoid request failures caused by instance exceptions. | |
GPU-accelerated instances | Feature iteration | Public preview of GPU-accelerated instances is complete and GPU-accelerated instances are available for commercial user. |
August 2022
Review type | Type | Description | References |
Official common layers | New | You can use the common layers provided by Function Compute to configure layers for your functions without the need to configure your own layers. | |
Canary release based on specified conditions for HTTP functions | New | Function Compute supports canary release based on specified conditions. Requests that meet the specified conditions are routed to canary release versions. | |
Running of new functions by the root user | Optimization | By default, new functions in Function Compute are run by root users, and existing functions are run by non-root users whose user IDs are greater than or equal to 10000. | - |
Directories to which data files can be written | Optimization | New functions in Function Compute can write files to all directories, not limited to the/tmp directory. | - |
July 2022
Review type | Type | Description | References |
Headers for HTTP functions | Optimization | The following request headers and response headers for HTTP functions are supported:
| |
System environment variables | New | The following system variables are supported:
|
June 2022
Review type | Type | Description | References |
EventBridge trigger API | Feature iteration | API operations for EventBridge triggers are supported. | |
Custom processing of cross-origin resource sharing (CORS) requests by HTTP functions | Optimization | By default, Function Compute allows you to invoke HTTP functions across origins. You can specify how functions process CORS requests in the code. |
May 2022
Review type | Type | Description | References |
Redirection to HTTPS | New | HTTP requests for custom domain names can be forcibly redirected to HTTPS. When Redirects HTTP Requests to HTTPS is enabled, Function Compute redirects all HTTP requests for the custom domain names to HTTPS. |
April 2022
Review type | Type | Description | References |
Asynchronous invocations for HTTP functions | New | HTTP functions are used to quickly build web applications. HTTP triggers support asynchronous invocations and asynchronous tasks. If the logic of your HTTP functions is time-consuming, resource-consuming, or error-prone, you can use asynchronous invocations to allow your programs to respond more quickly and reliably to traffic spikes. | |
WebSocket support for HTTP functions | New | HTTP functions can be triggered by WebSocket requests. An HTTP function works as a web server and processes WebSocket requests. | Configure an HTTP trigger for a function that is triggered by WebSocket requests |
Static public IP address | New | To allow Function Compute to access databases, WeChat mini programs, or third-party services, you need to configure a whitelist. You can use the static public IP address to verify the whitelist. |
March 2022
Review type | Type | Description | References |
Idle billing | New | The idle billing feature can be used on provisioned instances of Function Compute. By default, Function Compute allocates CPU resources to all provisioned instances. If the idle billing feature is enabled, only active instances are allocated with CPU resources. The unit prices of idle instance resources is 10% of the unit prices of resources for active instances. This helps you save your costs. | |
Domain name for HTTP triggers | Optimization | The domain name for HTTP triggers is changed to |