You need to enable JavaScript to run this app.
ByteHouse Cloud Data Warehouse Version

ByteHouse Cloud Data Warehouse Version

  • Documentation
    • ByteHouse Cloud Data Warehouse VersionByteHouse CDW calculate resources capacity planning best practices
Copy page
Download PDF
ByteHouse Cloud Data Warehouse Version
ByteHouse CDW calculate resources capacity planning best practices
Copy page
Download PDF
ByteHouse CDW calculate resources capacity planning best practices

This article aims to provide the Recommended dosage standards for ByteHouse cloud data warehouse Calculate Resources, and Intro how to Monitor and adjust according to these standards, to ensure stable business operation.

Recommended dosage standards

The main Calculate Resources of ByteHouse cloud data warehouse version are: virtual warehouse, dedicated Server, virtual warehouse local disk, and others. When you Buy these Calculate Resources for use, you need to Follow the dosage of Resources. When the dosage of Resources exceeds the risk threshold, the read/write Success rate will decrease. Therefore, it is Recommended to set corresponding Aarm Strategy for the dosage of Resources, and timely adjust the specifications of Calculate Resources at risk water level.
The following are the dosage standards for each Calculate Resources, of which,

  • Core dosage Metric: When using this Calculate Resources, you need to focus on this Metric. You can Request Tenant management > **** Cloud monitorModules to Get metric Data.
  • Recommended Resources water level: The safe waterline for Resources dosage. It is Recommended to stably maintain below this safe waterline.
  • low risk threshold: When Resources dosage has reached the low risk threshold, need to focus, mainly focus on dosage Trends, business read/write Flow Success rate. If the threshold is triggered occasionally, just keep continuous attention; if the Frequency is high (such as Every day), you need to plan the expansion of corresponding Calculate Resources.
  • high risk threshold: When Resources dosage has reached the high risk threshold, need to Immediately expand to prevent business loss.

Resource type

Core usage metric

Recommended resource water level

Low-risk threshold

High-risk threshold

Virtual warehouse

CPU usage rate

Stable less than 70%

Meet any of the following conditions:

  1. Continuous 10 min greater than 80%
  2. Continuous 30 min greater than 70%

Meet any of the following conditions:

  1. Continuous 10 min greater than 90%
  2. Continuous 30 min greater than 80%

Memory usage rate

Stable less than 70%

Meet any of the following conditions:

  1. Continuous 10 min greater than 80%
  2. Continuous 30 min greater than 70%

Meet any of the following conditions:

  1. Continuous 10 min greater than 90%
  2. Continuous 30 min greater than 80%

Dedicated Server

CPU usage rate

Stable less than 60%

Meet any of the following conditions:

  1. Continuous 10 min greater than 70%
  2. Continuous 30 min greater than 60%

Meet any of the following conditions:

  1. Continuous 10 min greater than 80%
  2. Continuous 30 min greater than 70%

Memory usage rate

Stable less than 60%

Meet any of the following conditions:

  1. Continuous 10 min greater than 70%
  2. Continuous 30 min greater than 60%

Meet any of the following conditions:

  1. Continuous 10 min greater than 80%
  2. Continuous 30 min greater than 70%

Virtual warehouse local disk

Disk utilization rate

Stable less than 70%

Meet any of the following conditions:

  1. Continuous 10 min greater than 80%
  2. Continuous 30 min greater than 70%

Meet any of the following conditions:

  1. Continuous 10 min greater than 90%
  2. Continuous 30 min greater than 80%

Disk IOPS (read) + Disk IOPS (write)

Total read/write IOPS, stable less than 60% * min{1800+50×capacity (GiB), 50000}

Meet any of the following conditions:

  1. Continuous 10 min greater than 70% * min{1800+50×capacity (GiB), 50000}
  2. Continuous 30 min greater than 60% * min{1800+50×capacity (GiB), 50000}

Meet any of the following conditions:

  1. Continuous 10 min greater than 80% * min{1800+50×capacity (GiB), 50000}
  2. Continuous 30 min greater than 70% * min{1800+50×capacity (GiB), 50000}

Disk bandwidth (read) + Disk bandwidth (write)

Total read/write bandwidth, stable less than 60% * min{120+0.5×capacity (GiB), 350}, unit: MB/s

Meet any of the following conditions:

  1. Continuous 10 min greater than 70% * min{120+0.5×capacity (GiB), 350}
  2. Continuous 30 min greater than 60% * min{120+0.5×capacity (GiB), 350}

Meet any of the following conditions:

  1. Continuous 10 min greater than 80% * min{120+0.5×capacity (GiB), 350}
  2. Continuous 30 min greater than 70% * min{120+0.5×capacity (GiB), 350}

Dosage Monitor Aarm and common adjustment methods

  1. All ByteHouse Resources dosage Data are pushed to BytePlus cloud Monitor Products. You can observe through the BytePlus cloud Monitor Console, or observe through the Tenant management > Cloud monitorPage on the ByteHouse cloud data warehouse version Console.

  2. Configure alarm methods. You can configure through the ByteHouse cloud data warehouse version Console. For Configuration Detail, please refer to Monitoring and alarm. At the same time, you can also configure settings in the BytePlus Cloud Monitor Console by referring to the ByteHouse cloud data warehouse version preset alert template. For operation details, see edit alert template.

  3. When usage metrics exceed the threshold, refer to the adjustment methods in the table below and make adjustments as needed.

    Rules

    Adjustment method

    Virtual warehouse

    CPU usage rate or CPU/memory usage rate triggers risk threshold

    1. Expand with the same type specification: for example, 2XL -> 3XL
    2. Expansion size is estimated based on reaching the recommended resource water level after expansion

    For virtual warehouse expansion operations, see Edit virtual warehouse configuration.

    If only memory usage rate triggers the risk threshold

    1. Change the specification type to performance type: for example, 2XL -> 2XL_PLUS
    2. The expansion size is estimated according to reaching the recommended resource watermark after expansion.

    For virtual warehouse expansion operations, please refer to Edit virtual warehouse configuration.

    CPU/memory usage exhibits periodic peaks and troughs over time.

    In the ByteHouse Console, use Task center > Create new task to create a virtual warehouse scaling task for scheduled elasticity. For operation details, please refer to Scheduled tasks.

    CPU/memory usage may fluctuate due to business load variations.

    You can use the ByteHouse load elasticity feature. For details, please refer to Load elasticity.

    Dedicated Server

    CPU usage or memory usage triggers the risk threshold.

    Scale up specifications: For example, 32 Core 128 GiB * 2 nodes -> 64 Core 256 GiB * 2 nodes. If higher specifications are required, you can contact the ByteHouse team.
    For dedicated Server expansion operations, please refer to Dedicated Server expansion.

    Virtual warehouse local disk

    Disk space utilization triggers the risk threshold.

    Expand the virtual warehouse local disk. The size is estimated according to reaching the recommended resource watermark after expansion.
    For local disk expansion operations, please refer to Edit virtual warehouse configuration.

    Disk bandwidth (read + write) triggers the risk threshold.

    1. When less than 350MB/s, you can expand the virtual warehouse local disk yourself. For local disk expansion operations, please refer to Edit virtual warehouse configuration.
    2. When reaching 350MB/s, you can contact the ByteHouse team for additional expansion.

    Disk IOPS (read + write) triggers the risk threshold.

    1. When less than 50000, you can expand the virtual warehouse local disk yourself. For local disk expansion operations, please refer to Edit virtual warehouse configuration.
    2. When reaching 50000, you can contact the ByteHouse team for additional expansion.
Last updated: 2026.03.31 20:05:27