Docs

Volcano Engine Function as a Service

Resource management

Function resource statistics

veFaaS allows you to set a resource usage upper limit for each function. This prevents resource contention among different functions within the same account. This also helps you manage the maximum number of concurrent instances, control costs, and prevent unexpected expenses. This topic introduces function-level resource statistical information. After the initial release of a function, you can go to the function details page and click the Resource management tab. Here, you can view the resource statistical information of the function.

Maximum resource

Memory specification: The memory specification of the function is that of the online revision. You can modify the memory specification of the function on the Function configuration tab. The modification takes effect only after the function is released.

Resource upper limit = Maximum number of instances ✖️ Function memory specification

Instance count range: This refers to the range from the minimum instance count to the maximum instance count. Click the edit icon to modify the minimum and maximum number of instances. For detailed operations, see Configuring static reserved instances.

Minimum number of instances: The number of reserved instances. The system will maintain and continuously run at least this number of instances until you set it to 0. Reserved instances are billed continuously while they are running. For billing details, see Product billing.

Maximum instance count: This is the maximum number of instances the function can scale to. You can adjust the maximum instance count to dynamically modify the resource limits of the function. We recommend setting the maximum instance count based on your business needs to prevent high costs caused by excessive function invocations.

tip

The maximum instance count applies per revision. For example, if you set the maximum instance count to 2, both the online and canary versions support up to 2 instances each.

Adjusting the maximum instance count is unavailable when a canary version of the function exists.

Usage ratio

The Usage ratio section displays the maximum resource size of the current function, the remaining available resource size of the account, and the ratio of the used resources for the current function to the resources of the account. For example, the preceding figure displays that the resources used by the current function account for 0.05% of the account resources.

Scheduled policy

When your function exhibits obvious periodic patterns or predictable traffic spikes, you can configure scheduled policies based on business characteristics to implement scheduled scaling of instances. This improves instance utilization and addresses resource waste. After a scheduled policy is configured, instances are dynamically scaled based on the policy, and the generated reserved instance names have a reserved identifier. For instructions on how to create a scheduled scaling policy for instances, see Reserved policies.

tip

You can configure autoscaling policies for microservice applications. You can select appropriate policies and metrics and set autoscaling target values to balance resource costs with stability based on your business scenario. For instructions on how to configure an autoscaling policy for microservice applications, see Autoscaling.

Instance list

The instance list displays the information about instances occupied by each online version of the current function, including the instance name, instance status, start time, instance logs, and Webshell. This helps you know the information about function instances.

Instance logs

Instance logs are the standard output logs of an instance, including instance startup logs, error logs, and business logs printed by the code. Compared to persistently stored TLS logs, function instance logs are more timely and are suitable for scenarios such as function debugging. If an instance is scaled in, its logs can no longer be viewed.

Find the target instance and click Logs in the Actions column to view the logs of the function instance.

You can click Auto refresh to load logs in real time.

You can switch log topics.

You can search for instances by keyword.

Webshell

With Webshell, you can log in to a function instance and run commands. For example, view the environment information of the instance and debug the function.

warning

Operate with caution after logging in to an instance. Your operations may affect live requests, and any resulting impact is excluded from SLA guarantees.

A single connection can last for up to 15 minutes and will automatically disconnect upon timeout. If you need to continue using it, log in again.

The runtimes provided by veFaaS have common Webshell tools installed by default. If you submit your business by using a custom image, make sure that any necessary Webshell tools are packaged into your image.

You can log in to only running function instances. If the instance is scaled in, the connection will be automatically terminated.

Find the target instance and click Webshell in the Actions column to log in to the instance. You can run commands based on your business requirements.

Migrate instancesWhen an exception occurs in an instance, you can migrate the instance. After migration, the original instance will be killed, and a new instance will be started. Find the target instance and click Migrate in the Actions column. After you confirm the operation, the instance migration will begin. When the instance state changes from Starting to Ready, the instance is migrated.

Last updated: 2026.08.19 14:06:06