Geekbench was skipped because this plan has less than 2 GB of RAM, which isn't enough for Geekbench 7 to run without swap.
Memory, TLS and scheduler
Memory bandwidth (STREAM)
Test
Result
Runs
Spread
Copy
higher is better
32.1 GB/s
3
8.84%
Scale
higher is better
22.4 GB/s
3
6.72%
Add
higher is better
26.9 GB/s
3
7.68%
Triad
higher is better
25.7 GB/s
3
6.4%
Average of 3 runs. Spread is the standard deviation as a share of the average.
TLS and crypto (OpenSSL)
Test
Result
Runs
Spread
RSA 4096 signs
higher is better
196/s
3
1.38%
RSA 4096 verifies
higher is better
12,815/s
3
1.49%
SHA-256
higher is better
737 MB/s
3
1.1%
AES-256-GCM
higher is better
3.34 GB/s
3
4.15%
ChaCha20-Poly1305
higher is better
1.97 GB/s
3
0.285%
Average of 3 runs. Spread is the standard deviation as a share of the average.
Scheduler latency (schbench)
Test
Result
Runs
Spread
Request latency, median
lower is better
5.02 ms
3
0.553%
Requests per second, 90th percentile
higher is better
196/s
3
0.51%
Request latency, 99.9th percentile
lower is better
13 ms
3
14%
Requests per second, average
higher is better
186/s
3
2.04%
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
Block size
Read
Write
Total
4K
122.1 MB/s (31,252 IOPS)
122.4 MB/s (31,334 IOPS)
244.5 MB/s (62,586 IOPS)
64K
1.4 GB/s (22,918 IOPS)
1.41 GB/s (23,039 IOPS)
2.81 GB/s (45,957 IOPS)
512K
3.41 GB/s (6,975 IOPS)
3.59 GB/s (7,346 IOPS)
6.99 GB/s (14,321 IOPS)
1M
2.35 GB/s (2,405 IOPS)
2.51 GB/s (2,565 IOPS)
4.85 GB/s (4,970 IOPS)
fio random read and write, 50/50, run by YABS against the boot disk.
Network
IPv4 transfer speed
Loading...
Target
Protocol
Send
Receive
Clouvider, London, UK (10G)
IPv4
1.03 Gbps
2.55 Gbps
Eranium, Amsterdam, NL (100G)
IPv4
1.04 Gbps
3.07 Gbps
Leaseweb, Singapore, SG (10G)
IPv4
848 Mbps
976 Mbps
Clouvider, Los Angeles, CA, US (10G)
IPv4
1.03 Gbps
3.14 Gbps
Leaseweb, NYC, NY, US (10G)
IPv4
1.1 Gbps
7.91 Gbps
Public iperf3 servers vary in capacity and availability. Compare a target only with itself over time.
Datastores
PostgreSQL
fsync speed (pg_test_fsync)
Method
Operations per second
Time per operation
One 8 kB write
open_datasync
9,474
0.106 ms
fdatasync
5,316
0.188 ms
fsync
3,774
0.265 ms
fsync_writethrough
Not supported here
n/a
open_sync
4,190
0.239 ms
Two 8 kB writes
open_datasync
4,267
0.234 ms
fdatasync
4,377
0.228 ms
fsync
3,282
0.305 ms
fsync_writethrough
Not supported here
n/a
open_sync
2,052
0.487 ms
open_sync at different write sizes
1 * 16kB open_sync write
3,951
0.253 ms
2 * 8kB open_sync writes
2,216
0.451 ms
4 * 4kB open_sync writes
1,098
0.911 ms
8 * 2kB open_sync writes
242
4.13 ms
16 * 1kB open_sync writes
133
7.51 ms
fsync on a non-write descriptor
write, fsync, close
3,390
0.295 ms
write, close, fsync
3,393
0.295 ms
Non-synced 8 kB writes
write
335,156
0.003 ms
pg_test_fsync against the Docker volume Postgres keeps its data on. fdatasync is Linux's default wal_sync_method.
pgbench at scale 10
Workload
Clients
Transactions/s
Median
p95
p99
p99.9
Failed
Read/write (TPC-B like)
1
1,502
0.576 ms
0.963 ms
1.77 ms
5.02 ms
0
Read/write (TPC-B like)
8
1,842
3.95 ms
6.99 ms
10.3 ms
18.6 ms
0
Read/write (TPC-B like)
32
1,634
16 ms
39.3 ms
68.2 ms
174 ms
0
Read only
1
18,962
0.043 ms
0.085 ms
0.217 ms
0.633 ms
0
Read only
8
19,093
0.32 ms
0.707 ms
1.18 ms
1.82 ms
0
Read only
32
18,378
1.31 ms
2.35 ms
3.33 ms
7.63 ms
0
Scale 10 (1,000,000 accounts), loaded in 2.51 s. 60 s per run, prepared statements. Latency comes from sampled transaction logs, and p99.9 is left out when fewer than 1,000 were sampled.
pgbench at scale 100
Workload
Clients
Transactions/s
Median
p95
p99
p99.9
Failed
Read/write (TPC-B like)
1
833
1.1 ms
1.88 ms
3.23 ms
8.78 ms
0
Read/write (TPC-B like)
8
1,296
5.27 ms
9.98 ms
24 ms
60.7 ms
0
Read/write (TPC-B like)
32
1,473
20 ms
31.4 ms
38.9 ms
57.1 ms
0
Read only
1
2,014
0.488 ms
0.828 ms
1.62 ms
4.58 ms
0
Read only
8
5,604
1.22 ms
2.79 ms
4.32 ms
12.1 ms
0
Read only
32
6,231
3.94 ms
8.07 ms
11.9 ms
19.6 ms
0
Scale 100 (10,000,000 accounts), loaded in 23.7 s. 60 s per run, prepared statements. Latency comes from sampled transaction logs, and p99.9 is left out when fewer than 1,000 were sampled.
MySQL
sysbench OLTP
Workload
Threads
Transactions/s
Queries/s
Median
p95
p99
Errors
Read/write
1
267
5,343
3.36 ms
6.32 ms
10.5 ms
0
Read/write
8
310
6,203
23.5 ms
44.2 ms
61.1 ms
0
Read/write
32
339
6,775
86 ms
162 ms
219 ms
0
Read only
1
651
10,424
1.39 ms
2.35 ms
3.62 ms
0
Read only
8
704
11,258
11 ms
15 ms
18.3 ms
0
Read only
32
642
10,276
48.3 ms
66.8 ms
77.2 ms
0
10 tables of 100,000 rows, loaded in 15.9 s. 60 s per run, one connection per thread.
Redis
memtier
Mix
Operations/s
Hits/s
Median
p99
p99.9
1:10 set:get
23,303
21,184
2.38 ms
6.11 ms
9.98 ms
1:1 set:get
23,145
11,572
2.38 ms
6.53 ms
12.7 ms
1,000,000 keys of 32 bytes. 64 connections over 1 thread, 60 s per ratio.
Web frameworks
Framework
Fortunes req/s
Single query req/s
JSON req/s
Fortunes p99 at 256 connections
Next.js
The results arrived but couldn't be read, so no numbers are shown.
Express
The results arrived but couldn't be read, so no numbers are shown.
Fastify
The results arrived but couldn't be read, so no numbers are shown.
NestJS
The results arrived but couldn't be read, so no numbers are shown.
Nuxt
The results arrived but couldn't be read, so no numbers are shown.
FastAPI
The results arrived but couldn't be read, so no numbers are shown.
Django
The results arrived but couldn't be read, so no numbers are shown.
Rails
The results arrived but couldn't be read, so no numbers are shown.
Laravel
The results arrived but couldn't be read, so no numbers are shown.
Symfony
The results arrived but couldn't be read, so no numbers are shown.
WooCommerce
Page mix
Step
Requests/s
Median
p95
p99
Error rate
8 virtual users
Home page
0.939
1.57 s
2.41 s
2.84 s
0%
Shop page
0.939
2.04 s
2.63 s
2.81 s
0%
Category page
0.939
1.77 s
2.18 s
2.27 s
0%
Product page
0.939
1.51 s
1.76 s
1.93 s
0%
Product search
0.939
1.39 s
1.51 s
1.53 s
0%
32 virtual users
Home page
0.941
5.67 s
6.4 s
6.46 s
0%
Shop page
0.941
7.48 s
8.78 s
9 s
0%
Category page
0.941
7.47 s
8.69 s
8.87 s
0%
Product page
0.941
6.51 s
7.51 s
7.61 s
0%
Product search
0.941
5.82 s
6.26 s
6.37 s
0%
Cart and checkout
Step
Requests/s
Median
p95
p99
Error rate
8 virtual users
Add to cart
1.9
1.44 s
1.77 s
1.82 s
0%
Cart
1.9
1.51 s
1.68 s
1.71 s
0%
Checkout
1.9
1.19 s
1.38 s
1.44 s
0%
32 virtual users
Add to cart
1.91
5.05 s
6.59 s
6.91 s
0%
Cart
1.91
6.03 s
6.68 s
6.87 s
0%
Checkout
1.91
4.93 s
5.59 s
5.66 s
0%
k6 with a fixed number of virtual users, 63 to 68 s per level. The error rate counts responses that weren't a 200.
Advertised vs. measured
Spec
Advertised
Measured
vCPU
1
1
CPU
Shared vCPU
2% of busy CPU time stolen
RAM
1 GB
961 MiB
Storage
25 GB SSD
24 GiB
Architecture
x86_64
x86_64
Virtualization
KVM
KVM
Guests usually report slightly less RAM and disk than advertised because of kernel reservations and filesystem overhead.
Detected hardware
CPU model
AMD EPYC 7713 64-Core Processor
CPU cores
1
CPU frequency
2000 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
961 MiB
Swap reported
496 MiB
Disk reported
24 GiB
Virtualization reported
KVM
CPU steal
2% of busy CPU time stolen
Distro
Ubuntu 24.04.4 LTS
Kernel
6.8.0-134-generic
Architecture
x86_64
IPv4 reachable
Yes
IPv6 reachable
Yes
Advertised at test time
Plan
Nanode 1GB
Product line
Shared CPU (Nanode)
Location
Newark, NJ
vCPU
1 shared vCPU
Architecture
x86_64
RAM
1 GB
Storage
25 GB SSD
Virtualization
KVM
Network
1 Gbps
Transfer
1 TB
Port 25
On request
Monthly price at test time
$5.00
Hourly price at test time
$0.0075
YABS version
v2026-09-20
Ran at
Oct 7, 2026, 00:21:12 UTC
Parser version
5
Run timeline
Queued
Oct 7, 2026, 00:17:00 UTC
First update from the server
Oct 7, 2026, 00:19:04 UTC
Completed
Oct 7, 2026, 01:30:37 UTC
Server deleted
Oct 7, 2026, 01:30:37 UTC
Cost of this run
$0.0092
TestResultTimevs last run
Started
00:17:00 UTC
Agent connected
00:19:02 UTC
Took
2m 03s
Server stats and output start when the agent connects.
Started
00:19:02 UTC
Took
2m 09s, 1m 22s last run
Avg CPU busy
6%
Avg CPU steal
0.3%
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
stopping background package jobs so they don't skew results
system settled, load average 0.23
downloading yabs v2026-09-20
Started
00:21:12 UTC
Took
0s, 0s last run
Output from this test
starting yabs -g -p lon.speedtest.clouvider.net:5200-5209:Clouvider:London UK (10G):IPv4,iperf-ams-nl.eranium.net:5201-5210:Eranium:Amsterdam NL (100G):IPv4,speedtest.sin1.sg.leaseweb.net:5201-5210:Leaseweb:Singapore SG (10G):IPv4,la.speedtest.clouvider.net:5200-5209:Clouvider:Los Angeles CA US (10G):IPv4,speedtest.nyc1.us.leaseweb.net:5201-5210:Leaseweb:NYC NY US (10G):IPv4 -w /opt/rackcensus/yabs.json
yabs is capped at 761 MB so a test that runs out of memory can't freeze the server
Started
00:21:12 UTC
Took
1s, 1s last run
Avg CPU busy
18%
Avg CPU steal
0.0%
Output from this test
yabs is capped at 761 MB so a test that runs out of memory can't freeze the server
Wed Oct 7 00:21:12 UTC 2026
Basic System Information:
Basic System Information:
Uptime : 0 days, 0 hours, 2 minutes
Processor : AMD EPYC 7713 64-Core Processor
CPU cores : 1 @ 1999.997 MHz
AES-NI :โ Enabled
VM-x/AMD-V :โ Disabled
RAM :961.5 MiB
Swap :496.0 MiB
Disk :24.0 GiB
Distro : Ubuntu 24.04.4 LTS
Kernel : 6.8.0-134-generic
VM Type : KVM
IPv4/IPv6 :โ Online / โ Online
IPv6 Network Information:
ISP : Akamai Technologies, Inc.
ASN : AS63949 Akamai Connected Cloud
Host : Linode
Location : Cedar Knolls, New Jersey (NJ)
Country : United States
Preparing system for disk tests...
TestResultTimevs last run
Started
00:21:13 UTC
Took
12s, 10s last run
Avg CPU busy
95%
Avg CPU steal
0.2%
Peak disk
1.68 GB/s
Avg I/O wait
0%
Read
Write
Waiting for the first server reading.
Output from this test
Generating fio test file...
Started
00:21:25 UTC
Took
17s, 12s last run
Avg CPU busy
96%
Avg CPU steal
0.0%
Peak disk
1.26 GB/s
Avg I/O wait
0%
Read
Write
Waiting for the first server reading.
Output from this test
Running fio random mixed R+W disk test with 4k block size...
Started
00:21:42 UTC
Took
2s, 2s last run
Avg CPU busy
79%
Avg CPU steal
0.0%
Peak disk
2.87 GB/s
Avg I/O wait
0%
Read
Write
Waiting for the first server reading.
Output from this test
Running fio random mixed R+W disk test with 64k block size...
Started
00:21:44 UTC
Took
1s, 1s last run
Avg CPU busy
69%
Avg CPU steal
0.0%
Peak disk
1.96 GB/s
Avg I/O wait
0%
Read
Write
Waiting for the first server reading.
Output from this test
Running fio random mixed R+W disk test with 512k block size...
Started
00:21:45 UTC
Took
1s, 1s last run
Avg CPU busy
49%
Avg CPU steal
0.0%
Peak disk
4.29 GB/s
Avg I/O wait
0%
Read
Write
Waiting for the first server reading.
Output from this test
Running fio random mixed R+W disk test with 1m block size...
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/sda):
Block Size | 4k (IOPS) | 64k (IOPS)
Read |128.00 MB/s(31.2k)|1.50 GB/s(22.9k)
Write |128.34 MB/s(31.3k)|1.50 GB/s(23.0k)
Total |256.35 MB/s(62.5k)|3.01 GB/s(45.9k)
Block Size | 512k (IOPS) | 1m (IOPS)
Read |3.65 GB/s(6.9k)|2.52 GB/s(2.4k)
Write |3.85 GB/s(7.3k)|2.69 GB/s(2.5k)
Total |7.50 GB/s(14.3k)|5.21 GB/s(4.9k)
TestResultTimevs last run
Started
00:21:46 UTC
Took
24s, 24s last run
Avg CPU busy
13%
Avg CPU steal
0.0%
Peak network
3.06 Gbit/s
Attempts
1 of 3
Send
1.03 Gbit/s
Receive
2.55 Gbit/s
Ping
72.0 ms
Server stats were not received during this test. This is the iperf3 result for this target.
Sent
Received
Waiting for the first server reading.
Output from this test
Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)...
Performing IPv4 iperf3 recv test from Clouvider (Attempt #1 of 3)...
Clouvider | London UK (10G) |1.03 Gbits/sec|2.55 Gbits/sec|72.0 ms
Started
00:22:10 UTC
Took
24s, 24s last run
Avg CPU busy
16%
Avg CPU steal
0.1%
Peak network
3.28 Gbit/s
Attempts
1 of 3
Send
1.04 Gbit/s
Receive
3.07 Gbit/s
Ping
77.4 ms
Server stats were not received during this test. This is the iperf3 result for this target.
Sent
Received
Waiting for the first server reading.
Output from this test
Performing IPv4 iperf3 send test to Eranium (Attempt #1 of 3)...
Performing IPv4 iperf3 recv test from Eranium (Attempt #1 of 3)...
Eranium | Amsterdam NL (100G) |1.04 Gbits/sec|3.07 Gbits/sec|77.4 ms
Started
00:22:34 UTC
Took
28s, 28s last run
Avg CPU busy
11%
Avg CPU steal
0.0%
Peak network
1.22 Gbit/s
Attempts
1 of 3
Send
848 Mbit/s
Receive
976 Mbit/s
Ping
224 ms
Server stats were not received during this test. This is the iperf3 result for this target.
Sent
Received
Waiting for the first server reading.
Output from this test
Performing IPv4 iperf3 send test to Leaseweb (Attempt #1 of 3)...
Performing IPv4 iperf3 recv test from Leaseweb (Attempt #1 of 3)...
Leaseweb | Singapore SG (10G) |848 Mbits/sec|976 Mbits/sec|224 ms
Started
00:23:02 UTC
Took
23s, 24s last run
Avg CPU busy
12%
Avg CPU steal
3.2%
Peak network
3.65 Gbit/s
Attempts
1 of 3
Send
1.03 Gbit/s
Receive
3.14 Gbit/s
Ping
59.9 ms
Server stats were not received during this test. This is the iperf3 result for this target.
Sent
Received
Waiting for the first server reading.
Output from this test
Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)...
Performing IPv4 iperf3 recv test from Clouvider (Attempt #1 of 3)...
Clouvider | Los Angeles CA US (10G) |1.03 Gbits/sec|3.14 Gbits/sec|59.9 ms
Started
00:23:26 UTC
Took
21s, 21s last run
Avg CPU busy
32%
Avg CPU steal
0.1%
Peak network
8.39 Gbit/s
Attempts
1 of 3
Send
1.10 Gbit/s
Receive
7.91 Gbit/s
Ping
2.43 ms
Server stats were not received during this test. This is the iperf3 result for this target.
Sent
Received
Waiting for the first server reading.
Output from this test
Performing IPv4 iperf3 send test to Leaseweb (Attempt #1 of 3)...
Performing IPv4 iperf3 recv test from Leaseweb (Attempt #1 of 3)...
Leaseweb | NYC NY US (10G) |1.10 Gbits/sec|7.91 Gbits/sec|2.43 ms
sysbench oltp_read_write with 1 threads did 267 tps
sysbench oltp_read_write with 8 threads
sysbench oltp_read_write with 8 threads did 310 tps
sysbench oltp_read_write with 32 threads
sysbench oltp_read_write with 32 threads did 339 tps
sysbench oltp_read_only with 1 threads
sysbench oltp_read_only with 1 threads did 651 tps
sysbench oltp_read_only with 8 threads
sysbench oltp_read_only with 8 threads did 704 tps
sysbench oltp_read_only with 32 threads
sysbench oltp_read_only with 32 threads did 642 tps
mysql/oltp passed
Started
00:51:55 UTC
Took
2m 51s
Avg CPU busy
97%
Avg CPU steal
0.3%
Peak memory
0.44 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
writing 1000000 keys
memtier 1:10 with 64 connections
memtier 1:10 did 23303 ops/s
memtier 1:1 with 64 connections
memtier 1:1 did 23145 ops/s
redis/memtier passed
TestResultTimevs last run
Started
00:54:47 UTC
Took
3m 07s
Avg CPU busy
96%
Avg CPU steal
0.1%
Peak memory
0.57 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Next.js with 1 workers
Next.js json primer at 8 connections
Next.js json warmup at 256 connections
Next.js json level at 64 connections
Next.js json at 64 connections did 1180 req/s
Next.js json level at 256 connections
Next.js json at 256 connections did 1195 req/s
Next.js db primer at 8 connections
Next.js db warmup at 256 connections
Next.js db level at 64 connections
Next.js db at 64 connections did 804 req/s
Next.js db level at 256 connections
Next.js db at 256 connections did 658 req/s
Next.js fortune primer at 8 connections
Next.js fortune warmup at 256 connections
Next.js fortune level at 64 connections
Next.js fortune at 64 connections did 210 req/s
Next.js fortune level at 256 connections
Next.js fortune at 256 connections did 191 req/s
frameworks/nextjs passed
Started
00:57:54 UTC
Took
2m 54s
Avg CPU busy
96%
Avg CPU steal
0.1%
Peak memory
0.46 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Express with 1 workers
Express json primer at 8 connections
Express json warmup at 256 connections
Express json level at 64 connections
Express json at 64 connections did 8470 req/s
Express json level at 256 connections
Express json at 256 connections did 8602 req/s
Express db primer at 8 connections
Express db warmup at 256 connections
Express db level at 64 connections
Express db at 64 connections did 5546 req/s
Express db level at 256 connections
Express db at 256 connections did 6168 req/s
Express fortune primer at 8 connections
Express fortune warmup at 256 connections
Express fortune level at 64 connections
Express fortune at 64 connections did 5334 req/s
Express fortune level at 256 connections
Express fortune at 256 connections did 6152 req/s
frameworks/express passed
Started
01:00:48 UTC
Took
2m 53s
Avg CPU busy
96%
Avg CPU steal
0.3%
Peak memory
0.46 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Fastify with 1 workers
Fastify json primer at 8 connections
Fastify json warmup at 256 connections
Fastify json level at 64 connections
Fastify json at 64 connections did 9848 req/s
Fastify json level at 256 connections
Fastify json at 256 connections did 10319 req/s
Fastify db primer at 8 connections
Fastify db warmup at 256 connections
Fastify db level at 64 connections
Fastify db at 64 connections did 6074 req/s
Fastify db level at 256 connections
Fastify db at 256 connections did 8013 req/s
Fastify fortune primer at 8 connections
Fastify fortune warmup at 256 connections
Fastify fortune level at 64 connections
Fastify fortune at 64 connections did 5218 req/s
Fastify fortune level at 256 connections
Fastify fortune at 256 connections did 5827 req/s
frameworks/fastify passed
Started
01:03:41 UTC
Took
3m 09s
Avg CPU busy
96%
Avg CPU steal
0.2%
Peak memory
0.55 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting NestJS with 1 workers
NestJS json primer at 8 connections
NestJS json warmup at 256 connections
NestJS json level at 64 connections
NestJS json at 64 connections did 5895 req/s
NestJS json level at 256 connections
NestJS json at 256 connections did 5659 req/s
NestJS db primer at 8 connections
NestJS db warmup at 256 connections
NestJS db level at 64 connections
NestJS db at 64 connections did 1982 req/s
NestJS db level at 256 connections
NestJS db at 256 connections did 1801 req/s
NestJS fortune primer at 8 connections
NestJS fortune warmup at 256 connections
NestJS fortune level at 64 connections
NestJS fortune at 64 connections did 1560 req/s
NestJS fortune level at 256 connections
NestJS fortune at 256 connections did 1522 req/s
frameworks/nestjs passed
Started
01:06:49 UTC
Took
2m 51s
Avg CPU busy
96%
Avg CPU steal
0.3%
Peak memory
0.48 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Nuxt with 1 workers
Nuxt json primer at 8 connections
Nuxt json warmup at 256 connections
Nuxt json level at 64 connections
Nuxt json at 64 connections did 10595 req/s
Nuxt json level at 256 connections
Nuxt json at 256 connections did 10674 req/s
Nuxt db primer at 8 connections
Nuxt db warmup at 256 connections
Nuxt db level at 64 connections
Nuxt db at 64 connections did 5607 req/s
Nuxt db level at 256 connections
Nuxt db at 256 connections did 5044 req/s
Nuxt fortune primer at 8 connections
Nuxt fortune warmup at 256 connections
Nuxt fortune level at 64 connections
Nuxt fortune at 64 connections did 4209 req/s
Nuxt fortune level at 256 connections
Nuxt fortune at 256 connections did 4004 req/s
frameworks/nuxt passed
Started
01:09:41 UTC
Took
3m 13s
Avg CPU busy
97%
Avg CPU steal
0.2%
Peak memory
0.44 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting FastAPI with 1 workers
FastAPI json primer at 8 connections
FastAPI json warmup at 256 connections
FastAPI json level at 64 connections
FastAPI json at 64 connections did 7071 req/s
FastAPI json level at 256 connections
FastAPI json at 256 connections did 6928 req/s
FastAPI db primer at 8 connections
FastAPI db warmup at 256 connections
FastAPI db level at 64 connections
FastAPI db at 64 connections did 1548 req/s
FastAPI db level at 256 connections
FastAPI db at 256 connections did 1436 req/s
FastAPI fortune primer at 8 connections
FastAPI fortune warmup at 256 connections
FastAPI fortune level at 64 connections
FastAPI fortune at 64 connections did 1286 req/s
FastAPI fortune level at 256 connections
FastAPI fortune at 256 connections did 1268 req/s
frameworks/fastapi passed
Started
01:12:53 UTC
Took
3m 16s
Avg CPU busy
97%
Avg CPU steal
0.3%
Peak memory
0.43 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Django with 1 workers
Django json primer at 8 connections
Django json warmup at 256 connections
Django json level at 64 connections
Django json at 64 connections did 1628 req/s
Django json level at 256 connections
Django json at 256 connections did 1659 req/s
Django db primer at 8 connections
Django db warmup at 256 connections
Django db level at 64 connections
Django db at 64 connections did 802 req/s
Django db level at 256 connections
Django db at 256 connections did 782 req/s
Django fortune primer at 8 connections
Django fortune warmup at 256 connections
Django fortune level at 64 connections
Django fortune at 64 connections did 731 req/s
Django fortune level at 256 connections
Django fortune at 256 connections did 655 req/s
frameworks/django passed
Started
01:16:10 UTC
Took
3m 15s
Avg CPU busy
97%
Avg CPU steal
0.1%
Peak memory
0.61 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Rails with 1 workers
Rails json primer at 8 connections
Rails json warmup at 256 connections
Rails json level at 64 connections
Rails json at 64 connections did 5085 req/s
Rails json level at 256 connections
Rails json at 256 connections did 4655 req/s
Rails db primer at 8 connections
Rails db warmup at 256 connections
Rails db level at 64 connections
Rails db at 64 connections did 1421 req/s
Rails db level at 256 connections
Rails db at 256 connections did 1388 req/s
Rails fortune primer at 8 connections
Rails fortune warmup at 256 connections
Rails fortune level at 64 connections
Rails fortune at 64 connections did 1125 req/s
Rails fortune level at 256 connections
Rails fortune at 256 connections did 1096 req/s
frameworks/rails passed
Started
01:19:25 UTC
Took
3m 02s
Avg CPU busy
97%
Avg CPU steal
0.1%
Peak memory
0.45 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Laravel with 2 workers
Laravel json primer at 8 connections
Laravel json warmup at 256 connections
Laravel json level at 64 connections
Laravel json at 64 connections did 577 req/s
Laravel json level at 256 connections
Laravel json at 256 connections did 590 req/s
Laravel db primer at 8 connections
Laravel db warmup at 256 connections
Laravel db level at 64 connections
Laravel db at 64 connections did 319 req/s
Laravel db level at 256 connections
Laravel db at 256 connections did 337 req/s
Laravel fortune primer at 8 connections
Laravel fortune warmup at 256 connections
Laravel fortune level at 64 connections
Laravel fortune at 64 connections did 307 req/s
Laravel fortune level at 256 connections
Laravel fortune at 256 connections did 319 req/s
frameworks/laravel passed
Started
01:22:27 UTC
Took
2m 59s
Avg CPU busy
97%
Avg CPU steal
0.1%
Peak memory
0.42 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Symfony with 2 workers
Symfony json primer at 8 connections
Symfony json warmup at 256 connections
Symfony json level at 64 connections
Symfony json at 64 connections did 1104 req/s
Symfony json level at 256 connections
Symfony json at 256 connections did 1015 req/s
Symfony db primer at 8 connections
Symfony db warmup at 256 connections
Symfony db level at 64 connections
Symfony db at 64 connections did 423 req/s
Symfony db level at 256 connections
Symfony db at 256 connections did 414 req/s
Symfony fortune primer at 8 connections
Symfony fortune warmup at 256 connections
Symfony fortune level at 64 connections
Symfony fortune at 64 connections did 377 req/s
Symfony fortune level at 256 connections
Symfony fortune at 256 connections did 405 req/s
frameworks/symfony passed
Started
01:25:26 UTC
Took
2m 58s
Avg CPU busy
96%
Avg CPU steal
0.2%
Peak memory
0.57 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting the store with 2 php-fpm workers
WooCommerce page mix with 8 virtual users
WooCommerce page mix at 8 virtual users did 4.7 req/s
WooCommerce page mix with 32 virtual users
WooCommerce page mix at 32 virtual users did 4.7 req/s
woocommerce/page_mix passed
Started
01:28:24 UTC
Took
2m 13s
Avg CPU busy
100%
Avg CPU steal
0.0%
Peak memory
0.62 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
WooCommerce cart flow with 8 virtual users
WooCommerce cart flow at 8 virtual users did 5.7 req/s
WooCommerce cart flow with 32 virtual users
WooCommerce cart flow at 32 virtual users did 5.7 req/s
woocommerce/cart_flow passed
TestResultTimevs last run
Started
01:30:37 UTC
Took
0s, 0s last run
Avg CPU busy
69%
Avg CPU steal
0.0%
Output from this test
No output from the server for this test yet.
Finished
Waiting for output from the server.
agent started on localhost
waiting for cloud-init to finish
stopping background package jobs so they don't skew results
system settled, load average 0.23
downloading yabs v2026-09-20
starting yabs -g -p lon.speedtest.clouvider.net:5200-5209:Clouvider:London UK (10G):IPv4,iperf-ams-nl.eranium.net:5201-5210:Eranium:Amsterdam NL (100G):IPv4,speedtest.sin1.sg.leaseweb.net:5201-5210:Leaseweb:Singapore SG (10G):IPv4,la.speedtest.clouvider.net:5200-5209:Clouvider:Los Angeles CA US (10G):IPv4,speedtest.nyc1.us.leaseweb.net:5201-5210:Leaseweb:NYC NY US (10G):IPv4 -w /opt/rackcensus/yabs.json
yabs is capped at 761 MB so a test that runs out of memory can't freeze the server