This topic describes release notes of Function Compute in 2022 and provides links to references.
November 2022
Feature | Type | Description | References |
Unit prices | Optimized | 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 | Optimized | The original memory specifications of instances are changed to vCPU specifications and memory specifications. | |
OSS file systems | 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 way as on-premises file systems. | |
GPU specifications | Optimized | GPU memory can be set to an integer value from 1 to 16. Unit: GB. |
September 2022
Feature | Type | Description | References |
Advanced features of EventBridge triggers | New | Advanced features such as batch push, retry, and dead-letter queues are supported by EventBridge triggers. | |
Runtimes
| New | The following runtimes are supported by 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 usage of streaming multiprocessors (SMs), GPU memory, hardware decoders, and hardware encoders. | |
gRPC protocol support for HTTP functions | New | HTTP functions can be triggered by gRPC requests. An HTTP function works as a web server that processes gRPC requests. | |
Non-web server mode | New | The non-web server mode is supported in Custom Container runtimes. 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 | Iterated | Public preview of GPU-accelerated instances is complete and GPU-accelerated instances are available for commercial user. |
August 2022
Feature | Type | Description | References |
Official common layers | New | Common layers are provided by Function Compute. You can directly use common layers for your functions without the need to configure custom layers. | |
Rule-based canary release for HTTP functions | New | Function Compute supports rule-based canary release. Requests that meet the specified rules are routed to canary release versions. | |
Root users | Optimized | By default, newly created functions in Function Compute are run by root users, and existing functions are run by non-root users whose user ID is greater than or equal to 10000. | None |
Directories to which data files can be written | Optimized | New functions in Function Compute can write files to all directories, instead of only the /tmp directory. | None |
July 2022
Feature | Type | Description | References |
Headers for HTTP functions | Optimized | The following request headers and response headers for HTTP functions are supported:
| |
System environment variables | New | The following system variables are supported:
|
June 2022
Feature | Type | Description | References |
EventBridge trigger API | Iterated | API operations for EventBridge triggers are supported. | |
CORS requests processing by HTTP functions | Optimized | By default, Function Compute allows you to invoke HTTP functions across origins. You can specify how functions process cross-origin resource sharing (CORS) requests in function code. |
May 2022
Feature | 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
Feature | 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 your HTTP function contains time-consuming, resource-consuming, or error-prone logic, 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 to processes WebSocket requests. | Configure an HTTP trigger for a function to respond to WebSocket requests |
Static public IP address | New | To allow Function Compute to access databases, WeChat mini programs, and third-party services, you need to configure a whitelist. You can configure a static public IP address to verify the whitelist. |
March 2022
Feature | 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 resources for idle instances are 10% of the unit prices of resources for active instances. This helps you save costs. | |
Domain name for HTTP triggers | Optimized | The domain name for HTTP triggers is changed to |