Skip to main content

Server Performance Requirements

CPU​

It is recommended to select processors with a clock speed ≥ 2.5 GHz.

High clock speed CPUs can provide faster computation and response speeds, ensuring system stability and smoothness in high-concurrency and complex computational scenarios.

Note:

  • Different CPU models vary in terms of clock speed and single-core performance. If the processor's single-core performance is insufficient, increasing the number of cores can enhance overall computing power to meet the needs of concurrent and multi-threaded tasks.
  • It is advisable to choose mainstream models released within the last 5 years to avoid outdated processors and ensure reliable performance.

Hard Drive​

Important Tips for Hard Drive Selection

  • 🚫 It is strictly prohibited to use mechanical hard drives (HDDs) in production environments

    • Typical IOPS performance for mechanical hard drives is only about 100, far below the minimum requirements.
    • Using HDDs will severely slow down the database and application system response times, posing significant performance risks, and may even lead to data consistency and security issues.

  • ✅ Use SSDs uniformly

    • All servers must uniformly use SSDs to ensure stability in scenarios involving large data volume access.
    • MongoDB is a core database in the HAP, and due to its high sensitivity to IO performance, it is recommended to prioritize NVMe SSDs for database services.

To assess the performance of SSDs, we used mid to low-range SSDs provided by common cloud vendors as a baseline.

The following are the minimum performance indicators. The actual configuration should not fall below these values, and exceeding them is preferable:

  • Random write performance: IOPS ≥ 15,000
  • Random read performance: IOPS ≥ 15,000
  • Sequential write speed: ≥ 200 MiB/s
  • Sequential read speed: ≥ 200 MiB/s

Cluster Mode - Intranet Network​

To ensure the stability and high performance of the cluster under various workloads, the intranet must meet the following requirements:

  • Intranet packet sending/receiving rate (PPS): Single server ≥ 200,000 PPS
  • Intranet bandwidth: Single server ≥ 2 Gbps

These requirements ensure that the system maintains stable, low-latency communication performance in high-load and large-scale data exchange scenarios.

Internet Bandwidth Requirements​

Recommended bandwidth: 30 Mbps or higher.
If the business involves a significant amount of file storage/download/upload, the bandwidth should be expanded further based on actual consumption.

📈 Why is Higher Bandwidth Needed?​

  • Accelerate Access: The larger the bandwidth, the faster the data transfer speed, resulting in a smoother user experience.
  • Support More Users: High bandwidth can prevent lag or delays during high concurrency, ensuring more users can be online simultaneously.
  • Handle Traffic Peaks: During peak business periods, adequate bandwidth ensures stable service operation, resisting sudden traffic surges.
  • Cost-effective: Cloud servers are recommended to use metered billing mode, ensuring transfer speed while being flexible enough to adapt to various business scales.

📊 Bandwidth Calculation Example​

Assuming a 30 Mbps bandwidth is chosen, with 30 users downloading files simultaneously:

  • Total Bandwidth: 30 Mbps = 30,000,000 bit/s
  • Bandwidth per User: 30,000,000 ÷ 30 = 1,000,000 bit/s
  • Download Speed per User: 1,000,000 ÷ 8 = 125,000 Byte/s ≈ 125 KB/s