Billing overview

更新时间:
复制 MD 格式

Function Compute bills usage in Compute Units (CUs). CU usage is derived by multiplying each billing factor — function invocations, active vCPU usage, idle vCPU usage, memory usage, disk usage, and active and idle GPU usage (Tesla series and Ada series) — by its CU conversion factor.

Function Compute supports three billing methods: free trial quotas, pay-as-you-go, and resource plans.

How CU usage is calculated

CU usage is calculated by multiplying each billing factor by its CU conversion factor:

Billing factor

Description

Function invocations

The total number of function invocations, whether triggered by event sources or called directly.

Active vCPU usage

vCPU time consumed while a function instance is actively processing a request.

Idle vCPU usage

vCPU time consumed while a provisioned function instance is idle, applicable only when idle mode is enabled.

Memory usage

Memory consumed by function instances during execution.

Disk usage

Disk space consumed by function instances.

Active GPU usage

GPU time consumed while a function instance is actively processing requests (Tesla series and Ada series).

Idle GPU usage

GPU time consumed while a provisioned function instance is idle when idle mode is enabled (Tesla series and Ada series).

For detailed pricing information, see Billing overview.

Billing methods

Billing method

How it works

Free trial quotas

A complimentary CU quota for first-time users. Usage within the quota is free each billing cycle. Excess usage is billed at pay-as-you-go rates unless you purchase a resource plan.

Resource plans

Function Compute offers five tiers of CU resource plans. A purchased plan offsets your usage first; when the quota is exhausted, charges revert to pay-as-you-go. Resource plans let you commit to a fixed volume at a discounted rate.

Pay-as-you-go

Charges are based on the computing resources your functions actually consume, with no upfront commitment.

Billing of other Alibaba Cloud services

Alibaba Cloud services that your functions access are billed separately under each service's pricing. Common examples include:

  • Object Storage Service (OSS) — for storing deployment packages, input data, and function output

  • Simple Log Service (SLS) — for collecting function execution logs

  • File Storage NAS — for functions that mount shared file systems

References