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
11.1 GB/s
3
0.639%
Scale
higher is better
12.9 GB/s
3
1.47%
Add
higher is better
13.3 GB/s
3
1.37%
Triad
higher is better
13.3 GB/s
3
1.27%
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
234/s
3
0.623%
RSA 4096 verifies
higher is better
15,355/s
3
0.0453%
SHA-256
higher is better
258 MB/s
3
0.121%
AES-256-GCM
higher is better
3.41 GB/s
3
0.146%
ChaCha20-Poly1305
higher is better
2.2 GB/s
3
0.0465%
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
7.74 ms
3
0%
Requests per second, 90th percentile
higher is better
255/s
3
0%
Request latency, 99.9th percentile
lower is better
29.5 ms
3
85.8%
Requests per second, average
higher is better
250/s
3
3.06%
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
Block size
Read
Write
Total
4K
6.1 MB/s (1,550 IOPS)
6 MB/s (1,548 IOPS)
12.1 MB/s (3,098 IOPS)
64K
64.5 MB/s (1,031 IOPS)
64.9 MB/s (1,038 IOPS)
129.4 MB/s (2,069 IOPS)
512K
62 MB/s (124 IOPS)
65 MB/s (129 IOPS)
127 MB/s (253 IOPS)
1M
61.4 MB/s (61 IOPS)
65.8 MB/s (65 IOPS)
127.2 MB/s (126 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.76 Gbps
1.43 Gbps
Eranium, Amsterdam, NL (100G)
IPv4
1.91 Gbps
2.94 Gbps
Leaseweb, Singapore, SG (10G)
IPv4
827 Mbps
1.09 Gbps
Clouvider, Los Angeles, CA, US (10G)
IPv4
1.69 Gbps
1.05 Gbps
Leaseweb, NYC, NY, US (10G)
IPv4
4.34 Gbps
3.22 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
1,197
0.835 ms
fdatasync
1,055
0.947 ms
fsync
347
2.88 ms
fsync_writethrough
Not supported here
n/a
open_sync
347
2.88 ms
Two 8 kB writes
open_datasync
532
1.88 ms
fdatasync
976
1.03 ms
fsync
337
2.97 ms
fsync_writethrough
Not supported here
n/a
open_sync
174
5.74 ms
open_sync at different write sizes
1 * 16kB open_sync write
339
2.95 ms
2 * 8kB open_sync writes
153
6.52 ms
4 * 4kB open_sync writes
69.6
14.4 ms
8 * 2kB open_sync writes
43.9
22.8 ms
16 * 1kB open_sync writes
21.9
45.6 ms
fsync on a non-write descriptor
write, fsync, close
345
2.9 ms
write, close, fsync
345
2.9 ms
Non-synced 8 kB writes
write
1,062,098
0.001 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
606
1.58 ms
2.19 ms
2.47 ms
13.5 ms
0
Read/write (TPC-B like)
8
2,255
3.04 ms
6.64 ms
10.9 ms
37.3 ms
0
Read/write (TPC-B like)
32
2,897
7.99 ms
29.8 ms
53.6 ms
93.1 ms
0
Read only
1
13,129
0.071 ms
0.095 ms
0.119 ms
0.356 ms
0
Read only
8
36,934
0.188 ms
0.355 ms
0.458 ms
0.753 ms
0
Read only
32
35,219
0.622 ms
1.35 ms
2.26 ms
3.6 ms
0
Scale 10 (1,000,000 accounts), loaded in 2.18 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
371
2.77 ms
3.23 ms
3.84 ms
14.4 ms
0
Read/write (TPC-B like)
8
998
5.72 ms
15.9 ms
20.6 ms
30.7 ms
0
Read/write (TPC-B like)
32
1,057
27.6 ms
50.1 ms
72.8 ms
154 ms
0
Read only
1
902
1.29 ms
1.53 ms
3.75 ms
7.41 ms
0
Read only
8
1,612
5.08 ms
9.98 ms
13 ms
26.6 ms
0
Read only
32
1,731
20 ms
30.5 ms
37.4 ms
228 ms
0
Scale 100 (10,000,000 accounts), loaded in 49.6 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
116
2,323
7.99 ms
12.3 ms
21.5 ms
0
Read/write
8
464
9,286
14.2 ms
41.9 ms
66.8 ms
0
Read/write
32
653
13,055
46.6 ms
74.5 ms
109 ms
0
Read only
1
472
7,551
1.96 ms
2.71 ms
3.62 ms
0
Read only
8
1,178
18,850
6.67 ms
9.73 ms
11.7 ms
0
Read only
32
1,133
18,122
25.7 ms
51.9 ms
61.1 ms
0
10 tables of 100,000 rows, loaded in 15.8 s. 60 s per run, one connection per thread.
Redis
memtier
Mix
Operations/s
Hits/s
Median
p99
p99.9
1:10 set:get
52,277
47,524
0.775 ms
3.58 ms
11.3 ms
1:1 set:get
52,145
26,072
0.775 ms
3.47 ms
8.77 ms
1,000,000 keys of 32 bytes. 64 connections over 2 threads, 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
Failed: woo-db stopped before it was ready: hysically writing the file full; Please wait ... 2026-10-07 0:20:05 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2026-10-07 0:20:05 0 [Note] InnoDB: log sequence number 45568; transaction id 14 2026-10-07 0:20:05 0 [Note] Plugin 'FEEDBACK' is disabled. 2026-10-07 0:20:05 0 [Note] Plugin 'wsrep-provider' is disabled. 2026-10-07 00:20:39+00:00 [ERROR] [Entrypoint]: Unable to start server.
Cart and checkout
Failed: k6 summary at 32 virtual users didn't parse: k6 recorded no requests for step checkout
Advertised vs. measured
Spec
Advertised
Measured
vCPU
2
2
CPU
Shared vCPU
15.5% of busy CPU time stolen
RAM
1 GB
910 MiB
Storage
40 GB SSD
38.7 GiB
Architecture
x86_64
x86_64
Virtualization
KVM
AMAZON
Guests usually report slightly less RAM and disk than advertised because of kernel reservations and filesystem overhead.
Detected hardware
CPU model
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
CPU cores
2
CPU frequency
2500 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
910 MiB
Swap reported
0 MiB
Disk reported
38.7 GiB
Virtualization reported
AMAZON
CPU steal
15.5% of busy CPU time stolen
Distro
Ubuntu 24.04.4 LTS
Kernel
7.0.0-1012-aws
Architecture
x86_64
IPv4 reachable
Yes
IPv6 reachable
Yes
Advertised at test time
Plan
Micro, 2 TB transfer
Product line
General Purpose
Location
Virginia
vCPU
2 shared vCPU
Architecture
x86_64
RAM
1 GB
Storage
40 GB SSD
Virtualization
KVM
Network
Unknown
Transfer
2.05 TB
Port 25
On request
Monthly price at test time
$7.00
Hourly price at test time
$0.0094
YABS version
v2026-09-20
Ran at
Oct 6, 2026, 23:05:44 UTC
Parser version
5
Run timeline
Queued
Oct 6, 2026, 23:04:00 UTC
First update from the server
Oct 6, 2026, 23:04:27 UTC
Completed
Oct 7, 2026, 00:24:46 UTC
Server deleted
Oct 7, 2026, 00:24:46 UTC
Cost of this run
$0.013
TestResultTimevs last run
Started
23:04:00 UTC
Agent connected
23:04:26 UTC
Took
27s
Server stats and output start when the agent connects.
Started
23:04:26 UTC
Took
1m 17s, 8s similar plans
Avg CPU busy
4%
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.47
downloading yabs v2026-09-20
Started
23:05:44 UTC
Took
0s, 0s similar plans
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 709 MB so a test that runs out of memory can't freeze the server
Started
23:05:44 UTC
Took
1s, 1s similar plans
Avg CPU busy
13%
Avg CPU steal
0.0%
Output from this test
Tue Oct 6 23:05:44 UTC 2026
Basic System Information:
Basic System Information:
Uptime : 0 days, 0 hours, 1 minutes
Processor : Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
CPU cores : 2 @ 2499.996 MHz
AES-NI :✔ Enabled
VM-x/AMD-V :❌ Disabled
RAM :909.5 MiB
Swap :0.0 KiB
Disk :38.7 GiB
Distro : Ubuntu 24.04.4 LTS
Kernel : 7.0.0-1012-aws
VM Type : AMAZON
IPv4/IPv6 :✔ Online / ✔ Online
IPv6 Network Information:
ISP : Amazon.com, Inc.
ASN : AS14618 Amazon.com, Inc.
Host : AWS EC2 (us-east-1)
Location : Ashburn, Virginia (VA)
Country : United States
Preparing system for disk tests...
TestResultTimevs last run
Started
23:05:45 UTC
Took
17s, 20s similar plans
Avg CPU busy
3%
Avg CPU steal
1.6%
Peak disk
208 MB/s
Avg I/O wait
79%
Read
Write
Waiting for the first server reading.
Output from this test
Generating fio test file...
Started
23:06:02 UTC
Took
31s, 31s similar plans
Avg CPU busy
2%
Avg CPU steal
2.7%
Peak disk
22.6 MB/s
Avg I/O wait
92%
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
23:06:33 UTC
Took
30s, 30s similar plans
Avg CPU busy
3%
Avg CPU steal
1.4%
Peak disk
202 MB/s
Avg I/O wait
93%
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
23:07:03 UTC
Took
31s, 31s similar plans
Avg CPU busy
2%
Avg CPU steal
0.1%
Peak disk
131 MB/s
Avg I/O wait
94%
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
23:07:34 UTC
Took
31s, 31s similar plans
Avg CPU busy
2%
Avg CPU steal
0.9%
Peak disk
131 MB/s
Avg I/O wait
93%
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/root):
Block Size | 4k (IOPS) | 64k (IOPS)
Read |6.35 MB/s(1.5k)|67.60 MB/s(1.0k)
Write |6.34 MB/s(1.5k)|68.03 MB/s(1.0k)
Total |12.69 MB/s(3.0k)|135.63 MB/s(2.0k)
Block Size | 512k (IOPS) | 1m (IOPS)
Read |65.01 MB/s(124)|64.38 MB/s(61)
Write |68.10 MB/s(129)|68.97 MB/s(65)
Total |133.12 MB/s(253)|133.36 MB/s(126)
TestResultTimevs last run
Started
23:08:05 UTC
Took
24s, 22s similar plans
Avg CPU busy
13%
Avg CPU steal
0.3%
Peak network
2.21 Gbit/s
Attempts
1 of 3
Send
1.76 Gbit/s
Receive
1.43 Gbit/s
Ping
79.8 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.76 Gbits/sec|1.43 Gbits/sec|79.8 ms
Started
23:08:29 UTC
Took
24s, 22s similar plans
Avg CPU busy
22%
Avg CPU steal
0.2%
Peak network
3.41 Gbit/s
Attempts
1 of 3
Send
1.91 Gbit/s
Receive
2.94 Gbit/s
Ping
93.3 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.91 Gbits/sec|2.94 Gbits/sec|93.3 ms
Started
23:08:53 UTC
Took
28s, 27s similar plans
Avg CPU busy
9%
Avg CPU steal
1.8%
Peak network
1.41 Gbit/s
Attempts
1 of 3
Send
827 Mbit/s
Receive
1.09 Gbit/s
Ping
233 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) |827 Mbits/sec|1.09 Gbits/sec|233 ms
Started
23:09:21 UTC
Took
23s, 26s similar plans
Avg CPU busy
12%
Avg CPU steal
0.3%
Peak network
1.93 Gbit/s
Attempts
1 of 3
Send
1.69 Gbit/s
Receive
1.05 Gbit/s
Ping
56.5 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.69 Gbits/sec|1.05 Gbits/sec|56.5 ms
Started
23:09:44 UTC
Took
21s, 24s similar plans
Avg CPU busy
34%
Avg CPU steal
6.2%
Peak network
4.88 Gbit/s
Attempts
1 of 3
Send
4.34 Gbit/s
Receive
3.22 Gbit/s
Ping
7.45 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) |4.34 Gbits/sec|3.22 Gbits/sec|7.45 ms
sysbench oltp_read_only with 32 threads did 1133 tps
mysql/oltp passed
Started
23:38:36 UTC
Took
2m 27s
Avg CPU busy
87%
Avg CPU steal
1.6%
Peak memory
0.49 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
server stats: posts recovered, 0 dropped, 0 rejected, backlog 0
writing 1000000 keys
memtier 1:10 with 64 connections
memtier 1:10 did 52277 ops/s
memtier 1:1 with 64 connections
memtier 1:1 did 52145 ops/s
redis/memtier passed
TestResultTimevs last run
Started
23:41:04 UTC
Took
3m 04s
Avg CPU busy
71%
Avg CPU steal
1.3%
Peak memory
0.63 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 1095 req/s
Next.js json level at 256 connections
Next.js json at 256 connections did 1349 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 999 req/s
Next.js db level at 256 connections
Next.js db at 256 connections did 804 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 206 req/s
Next.js fortune level at 256 connections
Next.js fortune at 256 connections did 102 req/s
frameworks/nextjs passed
Started
23:44:07 UTC
Took
2m 53s
Avg CPU busy
68%
Avg CPU steal
1.1%
Peak memory
0.51 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 11254 req/s
Express json level at 256 connections
Express json at 256 connections did 9914 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 7000 req/s
Express db level at 256 connections
Express db at 256 connections did 7420 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 6181 req/s
Express fortune level at 256 connections
Express fortune at 256 connections did 7142 req/s
frameworks/express passed
Started
23:47:00 UTC
Took
2m 51s
Avg CPU busy
70%
Avg CPU steal
1.4%
Peak memory
0.53 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 13079 req/s
Fastify json level at 256 connections
Fastify json at 256 connections did 10955 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 8357 req/s
Fastify db level at 256 connections
Fastify db at 256 connections did 10446 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 6398 req/s
Fastify fortune level at 256 connections
Fastify fortune at 256 connections did 7256 req/s
frameworks/fastify passed
Started
23:49:52 UTC
Took
3m 12s
Avg CPU busy
83%
Avg CPU steal
2.0%
Peak memory
0.59 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 4712 req/s
NestJS json level at 256 connections
NestJS json at 256 connections did 4482 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 756 req/s
NestJS db level at 256 connections
NestJS db at 256 connections did 656 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 512 req/s
NestJS fortune level at 256 connections
NestJS fortune at 256 connections did 508 req/s
frameworks/nestjs passed
Started
23:53:04 UTC
Took
2m 50s
Avg CPU busy
68%
Avg CPU steal
1.3%
Peak memory
0.54 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 12160 req/s
Nuxt json level at 256 connections
Nuxt json at 256 connections did 9895 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 6336 req/s
Nuxt db level at 256 connections
Nuxt db at 256 connections did 7426 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 4949 req/s
Nuxt fortune level at 256 connections
Nuxt fortune at 256 connections did 4939 req/s
frameworks/nuxt passed
Started
23:55:53 UTC
Took
3m 11s
Avg CPU busy
91%
Avg CPU steal
1.2%
Peak memory
0.53 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting FastAPI with 2 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 9507 req/s
FastAPI json level at 256 connections
FastAPI json at 256 connections did 9614 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 2751 req/s
FastAPI db level at 256 connections
FastAPI db at 256 connections did 2563 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 2200 req/s
FastAPI fortune level at 256 connections
FastAPI fortune at 256 connections did 2101 req/s
frameworks/fastapi passed
Started
23:59:05 UTC
Took
3m 11s
Avg CPU busy
89%
Avg CPU steal
2.1%
Peak memory
0.52 GiB
Busy
Steal
I/O wait
Waiting for the first server reading.
Output from this test
starting Django with 2 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 2063 req/s
Django json level at 256 connections
Django json at 256 connections did 2818 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 1285 req/s
Django db level at 256 connections
Django db at 256 connections did 1222 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 1115 req/s
Django fortune level at 256 connections
Django fortune at 256 connections did 996 req/s
frameworks/django passed
Started
00:02:16 UTC
Took
3m 28s
Avg CPU busy
52%
Avg CPU steal
11.3%
Peak memory
0.70 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 5913 req/s
Rails json level at 256 connections
Rails json at 256 connections did 5632 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 1483 req/s
Rails db level at 256 connections
Rails db at 256 connections did 1485 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 451 req/s
Rails fortune level at 256 connections
Rails fortune at 256 connections did 134 req/s
frameworks/rails passed
Started
00:05:44 UTC
Took
5m 43s
Avg CPU busy
8%
Avg CPU steal
67.6%
Peak memory
0.52 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 72 req/s
Laravel json level at 256 connections
Laravel json at 256 connections did 71 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 34 req/s
Laravel db level at 256 connections
Laravel db at 256 connections did 39 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 34 req/s
Laravel fortune level at 256 connections
Laravel fortune at 256 connections did 38 req/s
frameworks/laravel passed
Started
00:11:27 UTC
Took
5m 26s
Avg CPU busy
8%
Avg CPU steal
66.4%
Peak memory
0.48 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 151 req/s
Symfony json level at 256 connections
Symfony json at 256 connections did 143 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 43 req/s
Symfony db level at 256 connections
Symfony db at 256 connections did 45 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 39 req/s
Symfony fortune level at 256 connections
Symfony fortune at 256 connections did 43 req/s
frameworks/symfony passed
Started
00:16:53 UTC
Took
3m 48s
Avg CPU busy
7%
Avg CPU steal
56.6%
Peak memory
0.49 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 failed: woo-db stopped before it was ready: hysically writing the file full; Please wait ... 2026-10-07 0:20:05 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2026-10-07 0:20:05 0 [Note] InnoDB: log sequence number 45568; transaction id 14 2026-10-07 0:20:05 0 [Note] Plugin 'FEEDBACK' is disabled. 2026-10-07 0:20:05 0 [Note] Plugin 'wsrep-provider' is disabled. 2026-10-07 00:20:39+00:00 [ERROR] [Entrypoint]: Unable to start server.
Started
00:20:41 UTC
Took
4m 01s
Avg CPU busy
9%
Avg CPU steal
72.6%
Peak memory
0.62 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 cart flow with 8 virtual users
WooCommerce cart flow at 8 virtual users did 0.7 req/s
WooCommerce cart flow with 32 virtual users
woocommerce/cart_flow failed: k6 summary at 32 virtual users didn't parse: k6 recorded no requests for step checkout
TestResultTimevs last run
Started
00:24:46 UTC
Took
1s, 1s similar plans
Avg CPU busy
9%
Avg CPU steal
79.1%
Output from this test
No output from the server for this test yet.
Finished
Waiting for output from the server.
agent started on ip-172-26-0-75
waiting for cloud-init to finish
stopping background package jobs so they don't skew results
system settled, load average 0.47
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 709 MB so a test that runs out of memory can't freeze the server