Skip to main content

Server Performance Requirements

CPU​

It is recommended to use a processor with clock frequency ≥ 2.5 GHz.

High-frequency CPU can provide faster calculation and response speed, ensuring the stability and smoothness of the system in high-concurrency and complex computing scenarios.

Things to note:

  • Different models of CPU have differences in clock frequency and single-core performance. If the single-core performance of the processor is insufficient, the overall computing power can be increased by increasing the number of cores to meet the needs of concurrent and multi-threaded tasks.
  • It is recommended to choose mainstream models released within the past 5 years and avoid using old processors to ensure reliable performance.

Hard drive​

Important tips for hard drive selection

  • 🚫 It is strictly prohibited to use mechanical hard disks (HDD) in production environments

    • The typical IOPS performance of mechanical hard drives is only about 100, which is far below the minimum requirements.
    • Using HDD will seriously slow down the response speed of the database and application systems, bring extremely high performance risks, and may even cause data consistency and security risks.

  • ✅ Uniform use of SSD hard drives

    • All servers must use SSD uniformly to ensure stability in large data access scenarios.
    • MongoDB is the core database and because it is highly sensitive to IO performance, it is recommended to use NVMe SSD first for database services**.

In order to evaluate the performance of SSD hard drives, we used mid- to low-end SSDs provided by common cloud vendors as a benchmark.

The following are the minimum performance indicators. The actual configuration should be not lower than these values. If it can exceed them, it will be better:

  • 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 efficient performance of the cluster under various workloads, the intranet must meet the following requirements:

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

These requirements ensure that the system can still maintain stable and low-latency communication performance under high load and large-scale data exchange scenarios.

External network bandwidth requirements​

Recommended bandwidth: 30 Mbps and above. If the business involves a large number of file storage/download/upload functions, the bandwidth should be further expanded based on the actual bandwidth usage.

📈 Why do you need higher bandwidth?​

  • Accelerated Access: The larger the bandwidth, the faster the data transmission speed and the smoother user experience.
  • Support more users: High bandwidth can avoid lags or delays during high concurrency and ensure that more users are online at the same time.
  • Coping with traffic peaks: During peak business periods, sufficient bandwidth can ensure stable operation of services and withstand the impact of sudden traffic.
  • Better cost-effectiveness: It is recommended that the cloud server adopt the pay-by-traffic mode, which can not only ensure the transmission speed, but also flexibly adapt to business needs of different scales.

📊 Bandwidth calculation example​

Assuming 30 Mbps bandwidth is selected, if 30 users download files at the same time:

  • Total Bandwidth: 30 Mbps = 30,000,000 bit/s
  • Single user bandwidth: 30,000,000 ÷ 30 = 1,000,000 bit/s
  • Single user download speed: 1,000,000 ÷ 8 = 125,000 Byte/s ≈ 125 KB/s