Skip to main content
To benchmark a VPS, run YABS (Yet-Another-Bench-Script) with curl -sL yabs.sh | bash. It tests disk speed with fio, network throughput with iperf3 and CPU performance with Geekbench, then prints a summary. Skip parts with flags (-i no network, -g no Geekbench, -f no disk) or run fio directly. Benchmarks create heavy disk, CPU and network load, so run them once, at a quiet time.

​
Before you start

  • Connect with SSH. YABS doesn’t need root. sudo is only needed to install fio from your package manager; root users can leave it out.
  • Benchmark a fresh or quiet server. Anything else running (backups, game servers, databases) lowers the results and is slowed down by the test.
  • Results are a snapshot. Disk and network numbers on any virtual server vary from run to run and over the day, so compare several runs and don’t read too much into one.
Benchmarks are designed to push hardware to its limit. The YABS disk test writes a 2 GB file and hammers it for about 2 minutes; the network test tries to fill your connection for about 20 seconds per location. Your own services slow down while it runs, data transfer counts towards any traffic allowance, and repeated runs on shared hardware also load the host. Run a full benchmark once, not in a loop or from cron, and never on a production server during busy hours.

​
What do YABS, Geekbench and fio measure?

Small 4k block results show how the disk handles databases and many small files. Large 1m blocks show throughput for big files, backups and game world saves.

​
How to run YABS

1

Go to a folder on the disk you want to test

YABS tests the disk of the current directory and needs at least 2 GB free there (512 MB on ARM).
2

Download and read the script

Piping a script from the internet straight into bash runs whatever it contains. Download it first so you can see what it does:
3

Run it

For the full test:
For a lighter run with fewer network locations:
4

Wait for the report

YABS prints each section as it finishes. It removes its temporary test folder at the end. If Geekbench ran, it also writes the result’s claim link to geekbench_claim.url in the current folder.

​
Useful YABS flags

Combine flags: bash yabs.sh -ig runs the disk test only.
YABS uses fio and iperf3 from your system if they are installed; otherwise it downloads pre-built binaries from its GitHub repository. Geekbench is always downloaded from Primate Labs. On a server with 1 GB of RAM or less, Geekbench 5 and later can fail: add swap or use -4.

​
How to test disk speed with fio

Run fio yourself when you only care about the disk, or want to repeat the same test after a change.
1

Install fio

2

Random read and write (small files, databases)

3

Sequential write (large files)

4

Delete the test file

--direct=1 bypasses the page cache so you measure the disk, not RAM. --filename must point to a file.
Never point --filename at a device such as /dev/vda or /dev/sda on a server with data. A write test on a raw device overwrites the partition table and file systems on it, and the data is lost.

​
How to read fio output

​
How to run Geekbench on its own

Download the Linux build from geekbench.com, extract it and run the geekbench6 binary (or the binary for the version you downloaded). With no options it runs the CPU benchmark. In the free edition, results are saved to the online Geekbench Browser; Geekbench Pro can keep them offline. Compare scores only with the same Geekbench major version: a Geekbench 5 score and a Geekbench 6 score use different scales.

​
How to check it worked

A finished YABS run ends with the Geekbench section (or the last section you didn’t skip) and a total run time. Check no test file was left behind:
No output means nothing was left. If you stopped YABS with Ctrl+C, it cleans up its folder too.

​
Frequently asked questions

​
Is it safe to run yabs.sh?

The script is open source and doesn’t need root. As with any script from the internet, read it before you run it, and run it on a server where a few minutes of heavy load is acceptable.

​
Why are my results different every time?

Disk and network performance on virtual servers depends on activity elsewhere on the host and on the internet path to each iperf3 server. Run the test two or three times at different times and use the typical result.

​
Why is the network test slow to a far-away location?

TCP throughput drops as latency rises, so a server in Europe usually shows lower speeds to Asia or South America. That reflects distance, not a fault. For a test to your own endpoints, see test network speed with iperf3.

​
Can I benchmark a Windows server?

YABS supports Windows only through WSL 2. On Windows Server, use the Windows builds of Geekbench or fio instead, and the same caution about load applies.

VPS and dedicated server guides

Every server guide in one place.

Check disk I/O

iostat and iotop under real load.

Test network speed with iperf3

Measure throughput to your own server.

Find what is using CPU

When the CPU score looks low.

VPS traffic and bandwidth

How transfer is counted on your VPS.
Checked against the YABS README and script (version v2026-10-31), the fio documentation and Primate Labs’ Geekbench documentation on 4 November 2026; fio commands tested on Ubuntu 24.04 LTS (fio 3.36). YABS and Geekbench were not run. Commands can differ on other distributions or releases.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: November 2026