Billing Items
Billing Description
The billing items of FunctionGraph consist of requests, execution duration, and others. For details, see Table 1.
Billing Item |
Description |
Billing Mode |
Formula |
---|---|---|---|
Requests |
Total number of times all of your functions are invoked. |
Pay-per-use |
For details about the unit price of requests, see Pricing Details. |
Execution duration |
This billing item consists of two variables: execution duration and memory allocated to the function. FunctionGraph provides reserved and on-demand instances, which use compute resources differently. |
Pay-per-use |
- |
(1) If no reserved instances are used, the total compute resource consumption is the product of memory configured for a function and the execution duration. The execution duration is from the time your function code starts to execute to the time when it returns a response or terminates, and is rounded up to the nearest 1s. A duration of less than 1s is calculated as 1s. |
Compute resource consumption = Memory size (GB) x Execution duration (s)
For details about the unit price of execution duration, see Pricing Details. |
||
(2) If reserved instances are used, FunctionGraph starts billing when a reserved instance is created. If a reserved instance stays alive for less than 1 minute, you will be billed for 1 minute. Otherwise, you will be billed based on the actual duration, and the part beyond 1 minute will be rounded up to the nearest 1s. For details, see Reserved Instance Billing. |
The execution duration in the idle mode is not included in the 400,000 GB-second free quota. For details about the unit price of execution duration, see Pricing Details. |
||
Others |
Additional charges will apply if other cloud services, such as OBS and SMN, are used with FunctionGraph. |
Billing modes of involved services |
The billing modes of other cloud services are different. For details, see Pricing Details. |
Reserved Instance Billing
You can create and release reserved instances and will be billed based on their execution duration. Reserved instances stay alive in the execution environment, eliminating the influence of cold starts on latency.
- If you call an API to create a reserved instance, billing will begin as soon as the reserved instance creation is complete.
- If you call another API to release a reserved instance, new requests will not be routed to the reserved instance. The reserved instance will be released within a certain period, and the billing will stop.
As shown in Figure 1, the billing lasts from T1 to T4.
Reserved instances are metered at a granularity of second. If a reserved instance runs for any fraction of a minute, you will be billed for the full minute. Otherwise, you will be billed based on the actual execution duration.
For example, if a reserved instance runs for 51s, you will be billed for 1 minute. If the reserved instance runs for 61s, you will be billed for 61s.
- The unit of execution duration is GB-second, which means that when the memory size is 1 GB, the duration is charged by the second.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot