Reproducible evidence

VPS benchmarks with the settings attached.

A benchmark number needs the plan envelope, command, duration, timestamp and raw results. We publish the method and raw archive together.

01

Test identity

Disposable test guests use the same CPU, RAM and disk envelope as the published VPS 2 and VPS 4 plans. The guest OS, kernel, resource limits and run timestamp are recorded in the raw artifact.

02

CPU

sysbench CPU runs use a fixed max-prime and duration recorded with each result. vCPU is shared/scheduled capacity, so runs can vary; we preserve repeated results instead of selecting only the fastest sample.

03

Storage

fio jobs use explicit block size, queue depth, I/O engine, read/write mix, direct-I/O setting, file size and duration. The test file stays inside the disposable guest disk. We do not call a short synthetic fio run an application-performance guarantee.

04

Network and latency

Network tests record the endpoint and protocol. Results are point-in-time observations between controlled test endpoints and are not a Canada-wide latency or throughput promise.

05

Archive everything

Raw results live under data/benchmarks/vps/. Failed, noisy and unfavourable runs are retained with their status so later comparisons can see variance and methodology changes.

Latest certified run

VPS 2 and VPS 4 evidence.

Run ID: vps-benchmark-2026-09-01 · observed 2026-09-01

VPS 2

complete

Single-thread CPU 1,599.55 events/s; all-vCPU CPU 1,599.55 events/s; direct sequential write 2.28 GB/s; direct sequential read 6.93 GB/s; 4K 70/30 mixed read 79,728 read IOPS; controlled-endpoint download median 295.1 MB/s.

Open raw JSON evidence →

VPS 4

complete

Single-thread CPU 1,579.42 events/s; all-vCPU CPU 3,169.40 events/s; direct sequential write 2.55 GB/s; direct sequential read 7.10 GB/s; 4K 70/30 mixed read 86,935 read IOPS; controlled-endpoint download median 285.8 MB/s.

Open raw JSON evidence →

01

Evidence note

Results are short synthetic observations, not an uptime or workload guarantee.

02

Evidence note

Network numbers are point-in-time observations between controlled benchmark endpoints and are not a Canada-wide Internet throughput or latency promise.

03

Evidence note

The first VPS 2 measurement transport completed but its stdout was not retained; no claim is derived from that unretained attempt. The retained raw run below is the published VPS 2 evidence.