All Products
Search
Document Center

Lindorm:Billing of configuration changes

Last Updated:Mar 19, 2024

When you change the configurations of a Lindorm instance, the fees that you are charged for the instance changes. This topic describes the billing rules for the configuration changes of a Lindorm instance.

Fees incurred for the configuration changes of a pay-as-you-go instance

Fees for pay-as-you-go instances are billed on an hourly basis. After you change the configuration of a pay-as-you-go Lindorm instance, the fees are billed at the price of the new configuration from the current billing cycle.

Example: If you change the configuration of a pay-as-you-go Lindorm instance at 14:20, the fees for the instance during the billing cycle from 14:00 to 15:00 is billed at the price of the new configuration.

Fees incurred for the configuration changes of a subscription instance

You are charged fees for subscription instances before the instances are created. When you upgrade the configurations of a subscription instance, you are charged additional fees for the resources that are added to the instance after the upgrade. When you downgrade the configurations of a subscription instance, fees incurred by the resources that are removed from the instances are refunded.

Change method

Description

Upgrade

Billed fees = Total fees of the new configuration for the remaining subscription duration (Unit price of the new configuration × Remaining subscription duration) - Total fees of the original configurations for the remaining subscription duration (Unit price of the original configuration × Remaining subscription duration).

Example: The original configurations of the instance contain two LindormTable nodes each with 4 CPU cores and 16 GB of memory. The new configurations of the instance contain two LindormTable nodes each with 8 CPU cores and 16 GB of memory. The monthly price of the original configuration is USD 185.76. The monthly price of the new configuration is USD 312.63. The remaining subscription duration is 50 days. The fees for the configuration changes can be calculated by using the following formula: (312.63/30 × 50) - (185.76/30 × 50) = USD 211.45.

Important
  • The remaining subscription duration indicates the duration between the current time and the expiration time of the subscription instance. The remaining subscription duration is measured by second.

  • When you upgrade the configuration of an instance, the fees that is displayed on the upgrade page prevails.

Downgrade

For more information about refund rules for instance downgrade, see Request a refund for the downgrade of resource specifications.

FAQs

Why are the fees displayed on the configuration change page different from the fees displayed on the page a few days earlier?

Fees incurred for the configuration changes of a subscription instance depend on the remaining subscription duration of the instance and the difference between the original and new configurations.

The remaining subscription duration of an instance changes every day. Therefore, fees displayed on the upgrade page vary upon days.

You can check the expiration time of the instance on the configuration change page to calculate the remaining subscription duration of the instance.

Example: A subscription instance contains two LindormTable nodes each with 4 CPU cores, 16 GB of memory, and 480 GB of storage capacity. The monthly price for the instance is USD 185.76. You want to upgrade the LindormTable nodes to a specification that contains 8 CPU cores and 16 GB of memory. If the remaining subscription duration of the instance is 10 days, the fees incurred by the upgrade can be calculated by using the following formula: (312.63/30 × 10) - (185.76/30 × 10) = USD 42.29. If the remaining subscription duration of the instance is 5 days, the fees incurred by the upgrade can be calculated by using the following formula: (312.63/30 × 5) - (185.76/30 × 5) = USD 21.145.

Reference

For more information about how to change the configurations of an instance, see Modify the configurations of an instance.