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
10.4 GB/s
3
0.801%
Scale
higher is better
12.8 GB/s
3
1.65%
Add
higher is better
13.3 GB/s
3
1.7%
Triad
higher is better
13.7 GB/s
3
4.03%
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
233/s
3
0.559%
RSA 4096 verifies
higher is better
15,194/s
3
1.99%
SHA-256
higher is better
258 MB/s
3
0.146%
AES-256-GCM
higher is better
3.42 GB/s
3
0.0933%
ChaCha20-Poly1305
higher is better
2.21 GB/s
3
0.132%
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.72 ms
3
0.12%
Requests per second, 90th percentile
higher is better
257/s
3
0.225%
Request latency, 99.9th percentile
lower is better
26.8 ms
3
75.6%
Requests per second, average
higher is better
253/s
3
1.96%
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,549 IOPS)
6 MB/s (1,546 IOPS)
12.1 MB/s (3,095 IOPS)
64K
64.5 MB/s (1,031 IOPS)
64.9 MB/s (1,038 IOPS)
129.3 MB/s (2,069 IOPS)
512K
61.9 MB/s (123 IOPS)
64.8 MB/s (129 IOPS)
126.7 MB/s (252 IOPS)
1M
61.3 MB/s (61 IOPS)
65.7 MB/s (65 IOPS)
127 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.08 Gbps
779 Mbps
Eranium, Amsterdam, NL (100G)
IPv4
163 Mbps
1.91 Gbps
Leaseweb, Singapore, SG (10G)
IPv4
900 Mbps
1.34 Gbps
Clouvider, Los Angeles, CA, US (10G)
IPv4
2.91 Gbps
1.83 Gbps
Leaseweb, NYC, NY, US (10G)
IPv4
2.22 Gbps
2.45 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,054
0.949 ms
fdatasync
1,056
0.947 ms
fsync
349
2.87 ms
fsync_writethrough
Not supported here
n/a
open_sync
350
2.86 ms
Two 8 kB writes
open_datasync
531
1.88 ms
fdatasync
978
1.02 ms
fsync
339
2.95 ms
fsync_writethrough
Not supported here
n/a
open_sync
175
5.71 ms
open_sync at different write sizes
1 * 16kB open_sync write
341
2.93 ms
2 * 8kB open_sync writes
175
5.71 ms
4 * 4kB open_sync writes
80.9
12.4 ms
8 * 2kB open_sync writes
44.1
22.7 ms
16 * 1kB open_sync writes
22
45.4 ms
fsync on a non-write descriptor
write, fsync, close
347
2.89 ms
write, close, fsync
347
2.88 ms
Non-synced 8 kB writes
write
1,022,648
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
650
1.44 ms
2.14 ms
2.57 ms
15.5 ms
0
Read/write (TPC-B like)
8
2,360
3 ms
6.43 ms
9.4 ms
15.8 ms
0
Read/write (TPC-B like)
32
2,937
7.84 ms
28.5 ms
47.7 ms
90.9 ms
0
Read only
1
17,164
0.054 ms
0.071 ms
0.09 ms
0.242 ms
0
Read only
8
36,766
0.183 ms
0.371 ms
0.476 ms
0.634 ms
0
Read only
32
35,150
0.594 ms
1.34 ms
2.14 ms
3.41 ms
0
Scale 10 (1,000,000 accounts), loaded in 2.63 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
389
2.74 ms
3.05 ms
4.16 ms
8.28 ms
0
Read/write (TPC-B like)
8
996
5.95 ms
15.7 ms
19.4 ms
28 ms
0
Read/write (TPC-B like)
32
1,052
26.5 ms
47.3 ms
68.9 ms
155 ms
0
Read only
1
914
1.29 ms
1.48 ms
3.54 ms
5.94 ms
0
Read only
8
1,611
5.05 ms
9.69 ms
11.4 ms
14.6 ms
0
Read only
32
1,727
20 ms
30.5 ms
37.6 ms
340 ms
0
Scale 100 (10,000,000 accounts), loaded in 50 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
127
2,542
7.3 ms
10.8 ms
16.1 ms
0
Read/write
8
462
9,241
14 ms
46.6 ms
69.3 ms
0
Read/write
32
660
13,202
47.5 ms
73.1 ms
94.1 ms
0
Read only
1
628
10,040
1.5 ms
2.18 ms
2.97 ms
0
Read only
8
1,188
19,000
6.67 ms
9.73 ms
11.9 ms
0
Read only
32
1,103
17,656
28.7 ms
51.9 ms
61.1 ms
0
10 tables of 100,000 rows, loaded in 15.6 s. 60 s per run, one connection per thread.
Redis
memtier
Mix
Operations/s
Hits/s
Median
p99
p99.9
1:10 set:get
56,630
51,481
0.903 ms
2.86 ms
4.77 ms
1:1 set:get
52,731
26,365
0.831 ms
3.3 ms
6.85 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: k6 summary at 32 virtual users didn't parse: k6 recorded no requests for step category
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
11% 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 8259CL 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
11% 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
Oregon
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 7, 2026, 05:04:33 UTC
Parser version
5
Run timeline
Queued
Oct 7, 2026, 05:04:00 UTC
Server created
Oct 7, 2026, 05:04:26 UTC
First update from the server
Oct 7, 2026, 05:04:26 UTC
Completed
Oct 7, 2026, 06:24:45 UTC
Server deleted
Oct 7, 2026, 06:24:45 UTC
Cost of this run
$0.013
TestResultTimevs last run
Started
05:04:00 UTC
Agent connected
05:04:24 UTC
Took
24s
Server stats and output start when the agent connects.
Started
05:04:24 UTC
Took
8s, 7s last run
Avg CPU busy
34%
Avg CPU steal
0.1%
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.19
downloading yabs v2026-09-20
Started
05:04:32 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 709 MB so a test that runs out of memory can't freeze the server
Started
05:04:33 UTC
Took
1s, 1s last run
Output from this test
Wed Oct 7 05:04:33 UTC 2026
Basic System Information:
Basic System Information:
Uptime : 0 days, 0 hours, 0 minutes
Processor : Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
CPU cores : 2 @ 2499.998 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 : AS16509 Amazon.com, Inc.
Host : AWS EC2 (us-west-2)
Location : Boardman, Oregon (OR)
Country : United States
Preparing system for disk tests...
TestResultTimevs last run
Started
05:04:34 UTC
Took
17s, 20s last run
Avg CPU busy
3%
Avg CPU steal
0.0%
Peak disk
227 MB/s
Avg I/O wait
74%
Read
Write
Waiting for the first server reading.
Output from this test
Generating fio test file...
Started
05:04:51 UTC
Took
30s, 30s last run
Avg CPU busy
2%
Avg CPU steal
1.4%
Peak disk
75.5 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 4k block size...
Started
05:05:22 UTC
Took
30s, 30s last run
Avg CPU busy
3%
Avg CPU steal
0.3%
Peak disk
185 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 64k block size...
Started
05:05:52 UTC
Took
31s, 31s last run
Avg CPU busy
2%
Avg CPU steal
1.5%
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 512k block size...
Started
05:06:23 UTC
Took
31s, 31s last run
Avg CPU busy
2%
Avg CPU steal
0.0%
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 1m block size...
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/root):
Block Size | 4k (IOPS) | 64k (IOPS)
Read |6.34 MB/s(1.5k)|67.59 MB/s(1.0k)
Write |6.33 MB/s(1.5k)|68.02 MB/s(1.0k)
Total |12.68 MB/s(3.0k)|135.62 MB/s(2.0k)
Block Size | 512k (IOPS) | 1m (IOPS)
Read |64.90 MB/s(123)|64.29 MB/s(61)
Write |67.98 MB/s(129)|68.87 MB/s(65)
Total |132.89 MB/s(252)|133.16 MB/s(126)
TestResultTimevs last run
Started
05:06:54 UTC
Took
27s, 27s last run
Avg CPU busy
5%
Avg CPU steal
0.6%
Peak network
1.39 Gbit/s
Attempts
1 of 3
Send
1.08 Gbit/s
Receive
779 Mbit/s
Ping
148 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.08 Gbits/sec|779 Mbits/sec|148 ms
Started
05:07:21 UTC
Took
26s, 26s last run
Avg CPU busy
11%
Avg CPU steal
0.1%
Peak network
2.26 Gbit/s
Attempts
1 of 3
Send
163 Mbit/s
Receive
1.91 Gbit/s
Ping
142 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) |163 Mbits/sec|1.91 Gbits/sec|142 ms
Started
05:07:47 UTC
Took
28s, 28s last run
Avg CPU busy
10%
Avg CPU steal
0.2%
Peak network
1.67 Gbit/s
Attempts
1 of 3
Send
900 Mbit/s
Receive
1.34 Gbit/s
Ping
195 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) |900 Mbits/sec|1.34 Gbits/sec|195 ms
Started
05:08:14 UTC
Took
23s, 23s last run
Avg CPU busy
17%
Avg CPU steal
0.3%
Peak network
3.20 Gbit/s
Attempts
1 of 3
Send
2.91 Gbit/s
Receive
1.83 Gbit/s
Ping
29.7 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) |2.91 Gbits/sec|1.83 Gbits/sec|29.7 ms
Started
05:08:37 UTC
Took
26s, 24s last run
Avg CPU busy
17%
Avg CPU steal
2.8%
Peak network
3.84 Gbit/s
Attempts
2 of 3
Send
2.22 Gbit/s
Receive
2.45 Gbit/s
Ping
77.2 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 send test to Leaseweb (Attempt #2 of 3)...
Performing IPv4 iperf3 recv test from Leaseweb (Attempt #1 of 3)...
Leaseweb | NYC NY US (10G) |2.22 Gbits/sec|2.45 Gbits/sec|77.2 ms
sysbench oltp_read_write with 1 threads did 127 tps
sysbench oltp_read_write with 8 threads
sysbench oltp_read_write with 8 threads did 462 tps
sysbench oltp_read_write with 32 threads
sysbench oltp_read_write with 32 threads did 660 tps
sysbench oltp_read_only with 1 threads
sysbench oltp_read_only with 1 threads did 628 tps
sysbench oltp_read_only with 8 threads
sysbench oltp_read_only with 8 threads did 1188 tps
sysbench oltp_read_only with 32 threads
sysbench oltp_read_only with 32 threads did 1103 tps
mysql/oltp passed
Started
05:37:31 UTC
Took
2m 27s
Avg CPU busy
90%
Avg CPU steal
0.4%
Peak memory
0.49 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 56630 ops/s
memtier 1:1 with 64 connections
memtier 1:1 did 52731 ops/s
redis/memtier passed
TestResultTimevs last run
Started
05:39:59 UTC
Took
3m 05s
Avg CPU busy
71%
Avg CPU steal
1.1%
Peak memory
0.64 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 1380 req/s
Next.js json level at 256 connections
Next.js json at 256 connections did 1380 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 1000 req/s
Next.js db level at 256 connections
Next.js db at 256 connections did 792 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 211 req/s
Next.js fortune level at 256 connections
Next.js fortune at 256 connections did 105 req/s
frameworks/nextjs passed
Started
05:43:04 UTC
Took
2m 52s
Avg CPU busy
71%
Avg CPU steal
0.4%
Peak memory
0.52 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 13061 req/s
Express json level at 256 connections
Express json at 256 connections did 12461 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 6129 req/s
Express db level at 256 connections
Express db at 256 connections did 8449 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 6656 req/s
Express fortune level at 256 connections
Express fortune at 256 connections did 7662 req/s
frameworks/express passed
Started
05:45:56 UTC
Took
2m 51s
Avg CPU busy
70%
Avg CPU steal
0.7%
Peak memory
0.52 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 15145 req/s
Fastify json level at 256 connections
Fastify json at 256 connections did 13781 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 5823 req/s
Fastify db level at 256 connections
Fastify db at 256 connections did 8636 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 6881 req/s
Fastify fortune level at 256 connections
Fastify fortune at 256 connections did 8220 req/s
frameworks/fastify passed
Started
05:48:46 UTC
Took
3m 06s
Avg CPU busy
80%
Avg CPU steal
0.5%
Peak memory
0.60 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 8006 req/s
NestJS json level at 256 connections
NestJS json at 256 connections did 6082 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 690 req/s
NestJS db level at 256 connections
NestJS db at 256 connections did 660 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 539 req/s
NestJS fortune level at 256 connections
NestJS fortune at 256 connections did 518 req/s
frameworks/nestjs passed
Started
05:51:52 UTC
Took
2m 49s
Avg CPU busy
68%
Avg CPU steal
0.5%
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 12728 req/s
Nuxt json level at 256 connections
Nuxt json at 256 connections did 11942 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 5419 req/s
Nuxt db level at 256 connections
Nuxt db at 256 connections did 7749 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 4125 req/s
Nuxt fortune level at 256 connections
Nuxt fortune at 256 connections did 4969 req/s
frameworks/nuxt passed
Started
05:54:41 UTC
Took
3m 08s
Avg CPU busy
92%
Avg CPU steal
0.3%
Peak memory
0.52 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 8896 req/s
FastAPI json level at 256 connections
FastAPI json at 256 connections did 9387 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 2740 req/s
FastAPI db level at 256 connections
FastAPI db at 256 connections did 2707 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 2173 req/s
FastAPI fortune level at 256 connections
FastAPI fortune at 256 connections did 2095 req/s
frameworks/fastapi passed
Started
05:57:50 UTC
Took
3m 09s
Avg CPU busy
91%
Avg CPU steal
0.7%
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 3008 req/s
Django json level at 256 connections
Django json at 256 connections did 2842 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 1297 req/s
Django db level at 256 connections
Django db at 256 connections did 1089 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 1089 req/s
Django fortune level at 256 connections
Django fortune at 256 connections did 1007 req/s
frameworks/django passed
Started
06:00:59 UTC
Took
3m 16s
Avg CPU busy
61%
Avg CPU steal
1.4%
Peak memory
0.73 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 6394 req/s
Rails json level at 256 connections
Rails json at 256 connections did 6188 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 1608 req/s
Rails db level at 256 connections
Rails db at 256 connections did 1635 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 1154 req/s
Rails fortune level at 256 connections
Rails fortune at 256 connections did 1110 req/s
frameworks/rails passed
Started
06:04:15 UTC
Took
4m 02s
Avg CPU busy
12%
Avg CPU steal
68.4%
Peak memory
0.51 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 73 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 35 req/s
Laravel db level at 256 connections
Laravel db at 256 connections did 40 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 33 req/s
Laravel fortune level at 256 connections
Laravel fortune at 256 connections did 39 req/s
frameworks/laravel passed
Started
06:08:17 UTC
Took
5m 09s
Avg CPU busy
8%
Avg CPU steal
65.8%
Peak memory
0.47 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 153 req/s
Symfony json level at 256 connections
Symfony json at 256 connections did 151 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 47 req/s
Symfony db level at 256 connections
Symfony db at 256 connections did 49 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 44 req/s
Symfony fortune level at 256 connections
Symfony fortune at 256 connections did 48 req/s
frameworks/symfony passed
Started
06:13:26 UTC
Took
7m 12s
Avg CPU busy
8%
Avg CPU steal
66.3%
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 page mix with 8 virtual users
WooCommerce page mix at 8 virtual users did 0.6 req/s
WooCommerce page mix with 32 virtual users
woocommerce/page_mix failed: k6 summary at 32 virtual users didn't parse: k6 recorded no requests for step category
Started
06:20:43 UTC
Took
3m 58s
Avg CPU busy
9%
Avg CPU steal
74.9%
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
06:24:44 UTC
Took
1s, 1s last run
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-7-144
waiting for cloud-init to finish
stopping background package jobs so they don't skew results
system settled, load average 0.19
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