Help Center/ CodeArts PerfTest/ Billing/ Billing Modes/ Package Billing/ Duration-based Package Billing
Updated on 2025-08-29 GMT+08:00
View PDF
Share

Duration-based Package Billing

Application Scenarios

The duration-based package billing mode is cost-effective and useful for test tasks with predictable resource usage durations or that need to run 24/7. This mode is suitable for the following scenarios:

  • Workloads with long-term and stable resource demands, such as enterprise service systems.
  • Long-term projects, such as scientific research projects and large-scale events.
  • Workloads with predictable traffic bursts, for example, e-commerce promotions or festivals.
  • Workloads with high data security requirements.

Billing Items

Table 1 Billing items of duration-based packages

Billing Item

Description

Peak concurrency

Maximum number of concurrent users supported by a task. Estimate the value based on the test requirements.

Package duration

Validity of a duration-based package. The value can be 1 to 9 months or 1 year.

If you select One year, you enjoy the equivalent of two months free and only need to pay for 10 months.

Assume that you want to buy an Enterprise edition package with a peak concurrency of 1 million and a duration of 1 month. You can view the required configuration fees at the bottom of the Buy Package page.

Billing Cycle

The billing cycle of a CodeArts PerfTest duration-based package is determined by the purchased duration (GMT+08:00). The billing starts once you buy or renew a package (precise to seconds), and ends at 23:59:59 on the package's expiration date.

You can buy multiple packages as needed, but the durations of the packages do not accumulate. The expiration time is the latest expiration time among all packages.

For example, if you purchased a one-month package at 20:05:21 on April 9, 2023 and another one-month package at 16:51:20 on May 9, 2023, the combined validity period of these two packages is from 20:05:21 on April 9, 2023, to 23:59:59 on June 9, 2023.

Billing Example

Assume that you purchased a duration-based package with a peak concurrency of 1,000,000 and 1-month duration at 16:51:20 on May 9, 2023, and manually renewed it for 1 month before it expires.

  • First billing cycle: May 9, 2023, 16:51:20 to June 9, 2023, 23:59:59
  • Second billing cycle: June 10, 2023, 00:00:00 to July 9, 2023, 23:59:59

You need to prepay for each of the two billing cycles. If the price of a one-month package with a peak concurrency of 1,000,000 is $22,993 USD, you need to pay $22,993 USD for each cycle.

Impact of Expiration

Figure 1 describes the statuses of a duration-based package in each phase. After you buy a duration-based package, you can use CodeArts PerfTest properly within the billing cycle. This phase is the validity period. When the package expires and is not renewed, it goes into the grace period and then the retention period.

Figure 1 Duration-based package lifecycle
Before a duration-based package expires, the system will send an expiration reminder to the creator of the Huawei Cloud account by email, SMS, and internal message.
  • The system will send you a reminder 30 days, 15 days, 7 days, 3 days, and 1 day before a yearly resource expires.
  • The system will send you a reminder 15 days, 7 days, 3 days, and 1 day before a monthly resource expires.

If a duration-based package is not renewed after expiration, it goes into the grace period and its status changes to Grace Period. During this period, you can still use CodeArts PerfTest.

If you do not renew your package before the grace period ends, it goes into the retention period and its status turns to Frozen. If no other package is available in the retention period, test tasks cannot be started.

If the duration-based package is not renewed after the retention period expires, the package will be released. The data generated by CodeArts PerfTest is not affected, but pressure test tasks cannot be started.

Parent topic: Package Billing