VPSCheck usage tutorial: A must-do performance check for a new server

ℹ️

Disclosure: This article may contain affiliate links. If you purchase through these links, we may earn a small commission at no additional cost to you. All reviews are independently written and opinions remain unbiased.Learn more →

💡 AD: Get an extra 20% off Hostinger VPS Just Click Here

💡 Summary

  • After you get your new VPS, don’t rush to deploy the project.
  • First use the VPSCheck script to do a basic test to confirm whether the CPU, memory, disk and network are normal.
  • This article summarizes the complete usage process and results interpretation method, suitable for novices to get started quickly.
💡
💡

RackNerd — Editor's Pick

Get the best price through our exclusive link and support our reviews.

Explore RackNerd

The first step for many people after getting a VPS is to install the panel and deploy the website. In fact, a more reasonable order is to do a performance check first. VPSCheck is a common server detection script that can quickly check hardware information and basic performance to help determine whether there is overbooking or configuration abnormalities.

1. Preparation

First, you need to log in to the server through SSH.
Windows users can use the terminal or SSH tool; Mac/Linux users can enter directly in the terminal:

ssh root@your server IP

Enter the password to log in.

2. Run the VPSCheck script

After successfully logging in, copy the one-click command provided by the official warehouse and run it (it is recommended to obtain the latest command from the official project page). After execution, the script will automatically start to detect, including: CPU model and core number, memory size, disk type (SSD/NVMe), disk I/O read and write speed, system information, and network basic testing. The entire process usually takes 2–5 minutes. No operations are required during this period, just wait for the results to be output.

3. How to view the test results

  1. CPU information
    Confirm whether the model is consistent with the merchant's promotion and whether the number of cores is correct.

  2. Memory capacity
    Check whether it matches the purchase specifications.

  3. Disk I/O
    This is the point. Normal SSDs are usually a few hundred MB/s, NVMe will be even higher. If it's as low as tens of MB/s, there may be node congestion or severe overbooking.

  4. Virtualization type
    You can see whether it is KVM, OpenVZ or other architectures. KVM is usually more stable.

  5. Network test
    The network results are affected by the test node and can only be used as a reference and do not represent stable speeds all day long.

4. Precautions

Do not test when the server is under high load or during the evening peak, otherwise the I/O performance will be affected.
Do not run the script multiple times in a row, the disk test itself will generate load.
It is normal for test results to fluctuate. Do not draw conclusions based on one low score.

5. Correct use of mentality

VPSCheck is not a running score competition tool, but a physical examination tool. Its function is to help you determine whether the machine is obviously abnormal. If the test results are generally normal, you can deploy the project with confidence. What really determines the experience is long-term stability, not a beautiful running score.

Before a new VPS goes online, running a test is a habit worth developing.

🚀

Ready for RackNerd? Now is the perfect time

Use our exclusive link for the best price — and help support our content.

← Previous
vibe coding with cloudflare perfect match
Next →
The more centralized the small team technology stack, the lower the maintenance cost

🏷️ Related Keywords

💬 Comments

150 characters left

No comments yet. Be the first!

← Back to Articles