Release Notes
Product Announcements
Specification Adjustment | Billing Description |
Upgrading specifications | When users upgrade their compute node specifications, the system determines the cost difference between the current and upgraded node specifications. A bill is then generated, with the calculated difference deducted from the user's account. If the account balance is insufficient, a top-up is necessary. Following the upgrade, billing is based on the updated instance specifications. Cost difference = Unit price of new specifications × Validity period - Unit price of original specifications × Validity period |
Downgrading specifications | When users downgrade their compute node specifications, the system determines the cost difference between the current and downgraded node specifications. A bill is then generated, with the calculated difference refunded to the user's account. Refund amount = Remaining amount of the original specification - Purchase price of the new specification- Remaining amount for the original specification = Effective order amount of original specification - Used value of original specification. Effective order amount of original specification: The amount paid for the currently effective order, excluding discounts and vouchers. Used value of original specification: For the used part, if the usage has lasted at least one month as of the date of downgrade, fees will be deducted by month; otherwise, fees will be deducted in a pay-as-you-go manner. Purchase value of the new specification: The current official price of the new specification multiplied by the remaining validity period. |
Adding Read-only instances | The cost is charged according to the unit price of the newly purchased compute node. Cost of new read-only instances = Compute node unit price (USD/day) × Validity period |
Deleting instances | Both read-only instances and read-write instances can be deleted. For more information related to the cost of deleting instances, see Refund. Note: In a cluster with both read-write and read-only instances, delete the read-only instances first. Deleting the read-write instance is the same as returning the entire cluster. Alternatively, you can delete the entire cluster, removing both read-write and read-only instances. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback