VPS Benchmark Script Collection

Run a baseline after buying a VPS before deciding whether it is suitable for hosting, proxying, storage, or production services. This index groups the most useful tools by test target.

One-shot benchmarks

NodeQuality

NodeQuality is the simplest all-in-one option. It covers CPU, disk, network, IP quality, streaming access, and route information:

bash <(curl -fsSL https://raw.githubusercontent.com/xykt/NodeQuality/main/NodeQuality.sh)

bench.sh, and SuperBench

curl -fsL yabs.sh | bash
wget -qO- bench.sh | bash
bash <(wget -qO- https://raw.githubusercontent.com/spiritLHLS/superbench/main/superbench.sh)

These scripts run several tests at once and may write heavily to disk. Avoid business hours on production hosts.

Component tests

CPU

# Run the official Linux CLI after downloading Geekbench
./geekbench6

# UnixBench
git clone https://github.com/kdlucas/byte-unixbench.git
cd byte-unixbench/UnixBench && make && ./Run

Disk

fio is better suited than dd for comparing IOPS and queue depth. Do not run long random-write tests directly against a production disk.

sudo apt install -y fio
fio --name=randread --filename=/tmp/fio.test --size=1G --bs=4k \
  --rw=randread --ioengine=libaio --direct=1 --runtime=60 --time_based

Network, streaming, and IP quality

speedtest
bash <(curl -fsSL https://raw.githubusercontent.com/i-abc/speed-test/main/speedtest.sh)
iperf3 -c <server_ip> -t 30
bash <(curl -fsSL https://raw.githubusercontent.com/lmc999/RegionRestrictionCheck/main/check.sh)
bash <(curl -fsSL https://raw.githubusercontent.com/xykt/IPQuality/main/ip.sh)

Return routes

curl -fsSL https://raw.githubusercontent.com/zhanghanyun/backtrace/main/install.sh | sh
curl nxtrace.org/nt/install.sh | bash
nexttrace <target_ip>

Recommended workflow

Start with NodeQuality, then repeat with YABS, IPQuality, a streaming check, and backtrace when needed. Record the instance type, region, test time, disk type, and network limits so results remain comparable.

Safety notes

• Read remote scripts before running them; do not blindly use curl | bash on production hosts.
• Disk tests can create substantial writes. Use a temporary file, never a business data path.
• Public iperf3 servers are variable; treat their results as approximate.
• Do not publish public IPs, complete routes, or secrets with benchmark logs.
• Old bash.icu, ilemonra.in, and check.unlock.moe links are no longer reliable; use project repositories.

Target	Recommended tools
All-in-one	NodeQuality, YABS
CPU	Geekbench, UnixBench
Disk	fio
Network	Ookla, speed-test, iperf3
Streaming	RegionRestrictionCheck
IP quality	IPQuality
Return route	backtrace, NextTrace, BestTrace