OneProvider General Purpose GP1.2-2-40
Server
-
ProviderOneProvider
-
PlanGeneral Purpose GP1.2-2-40
-
LocationSeattle, US
-
vCPU2
-
RAM2 GB
-
Storage40 GB NVMe
-
Network10 Gbps
-
OS image1194
-
TriggerScheduled
-
Queued atOct 16, 2026, 22:01:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,224 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 3.1 GB of free memory to run 2 threads, and this server didn't have that much. Single-core needs much less, so it still ran.
Scores from different Geekbench versions aren't comparable with each other. Charts only use Geekbench 7.
Geekbench 7 workloads
| Workload | Single-core | Multi-core |
|---|---|---|
| File Compression |
1,197
|
Single-core only |
| Navigation |
1,300
|
Single-core only |
| HTML5 Browser |
1,225
|
Single-core only |
| PDF Viewer |
1,229
|
Single-core only |
| Photo Library |
1,096
|
Single-core only |
| Clang |
1,163
|
Single-core only |
| Text Processing |
1,060
|
Single-core only |
| Asset Compression |
1,210
|
Single-core only |
| HDR |
1,301
|
Single-core only |
| Photo Editor |
1,426
|
Single-core only |
| Ray Tracer |
1,258
|
Single-core only |
| Structure from Motion |
1,314
|
Single-core only |
| Game Physics |
1,274
|
Single-core only |
| Video Encoder |
1,178
|
Single-core only |
| Audio Encoder |
1,225
|
Single-core only |
| Video Player |
1,171
|
Single-core only |
Rank among the 216 runs with Geekbench 7 workload scores. Bars are relative to the best run. Geekbench doesn't run every workload multi-core, so some rows only have a single-core score.
Memory, TLS and scheduler
Memory bandwidth (STREAM)
| Test | Result | Runs | Spread |
|---|---|---|---|
| Copy higher is better | 65.1 GB/s | 3 | 1.14% |
| Scale higher is better | 66.7 GB/s | 3 | 2.08% |
| Add higher is better | 72.7 GB/s | 3 | 0.541% |
| Triad higher is better | 75.7 GB/s | 3 | 0.312% |
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 | 387/s | 3 | 0.517% |
| RSA 4096 verifies higher is better | 24,803/s | 3 | 0.62% |
| SHA-256 higher is better | 1.37 GB/s | 3 | 0.321% |
| AES-256-GCM higher is better | 6.31 GB/s | 3 | 0.508% |
| ChaCha20-Poly1305 higher is better | 3.59 GB/s | 3 | 0.343% |
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 | 4.37 ms | 3 | 0.211% |
| Requests per second, 90th percentile higher is better | 343/s | 3 | 0.292% |
| Request latency, 99.9th percentile lower is better | 30.1 ms | 3 | 0.96% |
| Requests per second, average higher is better | 341/s | 3 | 0.194% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 40.9 MB/s (10,472 IOPS) | 41 MB/s (10,495 IOPS) | 81.9 MB/s (20,967 IOPS) |
| 64K | 530.4 MB/s (8,486 IOPS) | 533.2 MB/s (8,531 IOPS) | 1.04 GB/s (17,017 IOPS) |
| 512K | 2.01 GB/s (4,113 IOPS) | 2.12 GB/s (4,331 IOPS) | 4.12 GB/s (8,444 IOPS) |
| 1M | 1.87 GB/s (1,913 IOPS) | 1.99 GB/s (2,040 IOPS) | 3.86 GB/s (3,953 IOPS) |
fio random read and write, 50/50, run by YABS against the boot disk.
Network
IPv4 transfer speed
| Target | Protocol | Send | Receive |
|---|---|---|---|
| Clouvider, London, UK (10G) | IPv4 | busy | 1.66 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1 Gbps | 1.66 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 622 Mbps | 1.16 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 2.65 Gbps | 2.69 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.42 Gbps | 2.3 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 | 2,885 | 0.347 ms |
| fdatasync | 2,981 | 0.335 ms |
| fsync | 1,851 | 0.54 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,927 | 0.519 ms |
| Two 8 kB writes | ||
| open_datasync | 1,518 | 0.659 ms |
| fdatasync | 2,905 | 0.344 ms |
| fsync | 1,821 | 0.549 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 955 | 1.05 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 1,945 | 0.514 ms |
| 2 * 8kB open_sync writes | 1,015 | 0.986 ms |
| 4 * 4kB open_sync writes | 538 | 1.86 ms |
| 8 * 2kB open_sync writes | 237 | 4.21 ms |
| 16 * 1kB open_sync writes | 117 | 8.52 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 2,037 | 0.491 ms |
| write, close, fsync | 1,805 | 0.554 ms |
| Non-synced 8 kB writes | ||
| write | 535,463 | 0.002 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,506 | 0.603 ms | 0.749 ms | 1.03 ms | 16.3 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,684 | 1.47 ms | 3.49 ms | 24.3 ms | 27.8 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,827 | 4.85 ms | 31 ms | 45.1 ms | 74.4 ms | 0 |
| Read only | 1 | 21,170 | 0.038 ms | 0.05 ms | 0.06 ms | 0.14 ms | 0 |
| Read only | 8 | 48,372 | 0.1 ms | 0.182 ms | 0.309 ms | 24.6 ms | 0 |
| Read only | 32 | 49,941 | 0.197 ms | 1.08 ms | 6.17 ms | 34.8 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.38 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 | 997 | 0.863 ms | 1.09 ms | 3.2 ms | 23.6 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,723 | 1.94 ms | 5.14 ms | 26.4 ms | 63.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,298 | 5.72 ms | 33.3 ms | 63.3 ms | 81 ms | 0 |
| Read only | 1 | 5,146 | 0.174 ms | 0.256 ms | 0.92 ms | 22.4 ms | 0 |
| Read only | 8 | 25,815 | 0.168 ms | 0.512 ms | 1.35 ms | 25.3 ms | 0 |
| Read only | 32 | 29,485 | 0.356 ms | 2.42 ms | 16.8 ms | 39 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 14.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 | 324 | 6,486 | 2.86 ms | 4.03 ms | 9.73 ms | 0 |
| Read/write | 8 | 730 | 14,591 | 8.28 ms | 32.5 ms | 38.9 ms | 0 |
| Read/write | 32 | 786 | 15,728 | 34.3 ms | 86 ms | 121 ms | 0 |
| Read only | 1 | 795 | 12,728 | 0.937 ms | 1.23 ms | 23.9 ms | 0 |
| Read only | 8 | 1,541 | 24,656 | 3.49 ms | 25.3 ms | 44.2 ms | 0 |
| Read only | 32 | 1,422 | 22,751 | 15.3 ms | 52.9 ms | 145 ms | 0 |
10 tables of 100,000 rows, loaded in 7.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 | 53,605 | 48,732 | 0.447 ms | 21.9 ms | 29.2 ms |
| 1:1 set:get | 53,733 | 26,866 | 0.447 ms | 21.9 ms | 37.1 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 nextjs | 591 | 2,085 | 3,097 | 707 ms |
| Express express-postgresjs | 5,862 | 9,002 | 32,469 | 81.9 ms |
| Fastify fastify-postgres | 5,641 | 9,451 | 37,811 | 99 ms |
| NestJS nestjs | 4,637 | 5,100 | 18,876 | 106 ms |
| Nuxt nuxt | 5,295 | 9,111 | 35,702 | 104 ms |
| FastAPI fastapi | 3,431 | 4,224 | 21,372 | 407 ms |
| Django django-postgresql | 1,441 | 1,515 | 3,269 | 299 ms |
| Rails rails | 2,336 | 2,974 | 11,971 | 140 ms |
| Laravel laravel | 742 | 785 | 1,451 | 385 ms |
| Symfony symfony | 920 | 1,018 | 2,811 | 305 ms |
Peak requests per second across the 64 and 256 connection levels, measured with wrk. Each test has to pass the TechEmpower response checks first, or it's marked invalid.
Web apps
WooCommerce
Page mix
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Home page | 2.24 | 697 ms | 938 ms | 1.07 s | 0% |
| Shop page | 2.24 | 931 ms | 1.26 s | 1.39 s | 0% |
| Category page | 2.24 | 608 ms | 961 ms | 1.12 s | 0% |
| Product page | 2.24 | 646 ms | 901 ms | 984 ms | 0% |
| Product search | 2.24 | 550 ms | 789 ms | 826 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.27 | 2.58 s | 3.07 s | 3.22 s | 0% |
| Shop page | 2.27 | 3.34 s | 3.84 s | 4.13 s | 0% |
| Category page | 2.27 | 3 s | 3.62 s | 3.82 s | 0% |
| Product page | 2.27 | 2.6 s | 2.91 s | 3.04 s | 0% |
| Product search | 2.2 | 2.4 s | 2.72 s | 2.79 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.33 | 728 ms | 993 ms | 1.12 s | 0% |
| Cart | 4.33 | 607 ms | 825 ms | 903 ms | 0% |
| Checkout | 4.33 | 466 ms | 693 ms | 778 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.38 | 2.49 s | 3.04 s | 3.25 s | 0% |
| Cart | 4.38 | 2.6 s | 2.92 s | 3.12 s | 0% |
| Checkout | 4.38 | 2.11 s | 2.47 s | 2.57 s | 0% |
k6 with a fixed number of virtual users, 62 to 70 s per level. The error rate counts responses that weren't a 200.
Discourse
Signed in
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Topic page | 2.88 | 156 ms | 182 ms | 338 ms | 0% |
| Topic JSON | 1.44 | 76.7 ms | 99.9 ms | 190 ms | 0% |
| Home page | 1.44 | 144 ms | 179 ms | 286 ms | 0% |
| Categories page | 0.729 | 160 ms | 176 ms | 181 ms | 0% |
| User activity page | 0.713 | 92.1 ms | 112 ms | 338 ms | 0% |
| 4 virtual users | |||||
| Topic page | 4.24 | 429 ms | 574 ms | 782 ms | 0% |
| Topic JSON | 2.14 | 210 ms | 298 ms | 371 ms | 0% |
| Home page | 2.12 | 387 ms | 615 ms | 1.04 s | 0% |
| Categories page | 1.08 | 438 ms | 584 ms | 779 ms | 0% |
| User activity page | 1.06 | 250 ms | 407 ms | 710 ms | 0% |
| 16 virtual users | |||||
| Topic page | 4.02 | 1.48 s | 1.85 s | 1.99 s | 0% |
| Topic JSON | 2 | 1.29 s | 1.7 s | 2 s | 0% |
| Home page | 1.93 | 1.46 s | 1.82 s | 1.99 s | 0% |
| Categories page | 1.01 | 1.5 s | 1.85 s | 1.94 s | 0% |
| User activity page | 0.992 | 1.36 s | 1.68 s | 1.88 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 71.6 | 67.7 ms | 152 ms | 198 ms | 0% |
| Topic JSON | 35.8 | 67.9 ms | 150 ms | 204 ms | 0% |
| Home page | 35.9 | 70.8 ms | 156 ms | 200 ms | 0% |
| Categories page | 17.9 | 67.8 ms | 149 ms | 195 ms | 0% |
| User activity page | 18 | 196 ms | 354 ms | 513 ms | 0% |
k6 with a fixed number of virtual users, 60 to 62 s per level, after a 21 s warmup. The error rate counts responses that weren't a 200. Discourse ran with 4 app workers and 256 MB of Postgres shared buffers, what its installer picks for a 2 GB box. It added a 2 GB swapfile first, the way its installer does, and used up to 380 MB of it. The container peaked at 1,487 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 9.5 | 25.4 ms | 47.5 ms | 54.8 ms | 0% |
| Post page | 23.7 | 12.7 ms | 34.2 ms | 38.4 ms | 0% |
| Tag page | 4.75 | 17.5 ms | 40.1 ms | 51.2 ms | 0% |
| Author page | 4.75 | 17 ms | 38.4 ms | 41.3 ms | 0% |
| RSS feed | 4.73 | 22.1 ms | 44.2 ms | 49.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 10.4 | 102 ms | 145 ms | 182 ms | 0% |
| Post page | 26 | 72.6 ms | 102 ms | 153 ms | 0% |
| Tag page | 5.21 | 63.7 ms | 91.3 ms | 148 ms | 0% |
| Author page | 5.2 | 64.8 ms | 88.6 ms | 112 ms | 0% |
| RSS feed | 5.16 | 72.2 ms | 99.1 ms | 122 ms | 0% |
| 16 virtual users | |||||
| Home page | 10.4 | 389 ms | 490 ms | 518 ms | 0% |
| Post page | 26.1 | 313 ms | 413 ms | 455 ms | 0% |
| Tag page | 5.2 | 210 ms | 300 ms | 332 ms | 0% |
| Author page | 5.23 | 209 ms | 299 ms | 331 ms | 0% |
| RSS feed | 5.18 | 217 ms | 317 ms | 345 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.43 | 25.4 ms | 44.5 ms | 60.6 ms | 0% |
| Post editor | 16.3 | 8.75 ms | 24.6 ms | 29.5 ms | 0% |
| Saving a draft | 16.3 | 24.2 ms | 43.1 ms | 55.3 ms | 0% |
| Member list | 5.43 | 28.7 ms | 45.9 ms | 51.7 ms | 0% |
| 4 virtual users | |||||
| Post list | 6.2 | 37.4 ms | 60.5 ms | 92.1 ms | 0% |
| Post editor | 18.6 | 15.1 ms | 39.8 ms | 55.1 ms | 0% |
| Saving a draft | 18.7 | 159 ms | 222 ms | 270 ms | 0% |
| Member list | 6.21 | 40.3 ms | 63.2 ms | 106 ms | 0% |
k6 with a fixed number of virtual users, 60 s per level, after a 20 s warmup. The error rate counts responses that weren't a 200. Ghost ran the way its ghost-docker setup runs it: one Node process, and MySQL with its stock 128 MB buffer pool. Memory peaked with Ghost at 358 MB and MySQL at 586 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 2.09 | 58.3 ms | 71.3 ms | 78.3 ms | 0% |
| Blog index | 2.09 | 235 ms | 253 ms | 267 ms | 0% |
| Blog post | 6.24 | 18.9 ms | 29.3 ms | 43.2 ms | 0% |
| Bread page | 6.26 | 20.8 ms | 25.5 ms | 41.5 ms | 0% |
| Location page | 2.09 | 19.7 ms | 22.7 ms | 24.5 ms | 0% |
| Site search | 2.07 | 32.9 ms | 60.9 ms | 68.9 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.88 | 191 ms | 246 ms | 272 ms | 0% |
| Blog index | 2.92 | 702 ms | 840 ms | 927 ms | 0% |
| Blog post | 8.67 | 56.5 ms | 91.7 ms | 114 ms | 0% |
| Bread page | 8.68 | 60.3 ms | 87.8 ms | 102 ms | 0% |
| Location page | 2.93 | 53.7 ms | 81.7 ms | 192 ms | 0% |
| Site search | 2.87 | 86.4 ms | 164 ms | 186 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.82 | 668 ms | 906 ms | 1.11 s | 0% |
| Blog index | 2.82 | 1.71 s | 2.03 s | 2.19 s | 0% |
| Blog post | 8.36 | 372 ms | 612 ms | 685 ms | 0% |
| Bread page | 8.41 | 378 ms | 601 ms | 718 ms | 0% |
| Location page | 2.79 | 375 ms | 582 ms | 672 ms | 0% |
| Site search | 2.79 | 449 ms | 666 ms | 781 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.808 | 61.2 ms | 82.2 ms | 89.8 ms | 0% |
| Page explorer | 1.63 | 300 ms | 338 ms | 458 ms | 0% |
| Page editor | 2.43 | 136 ms | 177 ms | 271 ms | 0% |
| Image library | 0.808 | 47.9 ms | 72.6 ms | 590 ms | 0% |
| Admin page search | 0.808 | 25.1 ms | 70.2 ms | 138 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.26 | 229 ms | 408 ms | 583 ms | 0% |
| Page explorer | 2.56 | 759 ms | 1.07 s | 1.12 s | 0% |
| Page editor | 3.82 | 355 ms | 610 ms | 674 ms | 0% |
| Image library | 1.28 | 195 ms | 364 ms | 396 ms | 0% |
| Admin page search | 1.26 | 86.4 ms | 249 ms | 306 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 s per level, after a 20 s warmup. The error rate counts responses that weren't a 200. Wagtail ran the way bakerydemo ships it: uWSGI with 2 workers of 4 threads each, whatever the box, and Postgres and Redis on stock settings. Memory peaked with Wagtail at 299 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 20.8% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 40 GB NVMe | 38.8 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 Processor
- CPU cores
- 2
- CPU frequency
- 3250 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 1.9 GiB
- Swap reported
- 512 MiB
- Disk reported
- 38.8 GiB
- Virtualization reported
- KVM
- CPU steal
- 20.8% of busy CPU time stolen
- Distro
- Ubuntu 24.04.3 LTS
- Kernel
- 6.8.0-79-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- No
Advertised at test time
- Plan
- General Purpose GP1.2-2-40
- Product line
- General Purpose
- Location
- Seattle, US
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 40 GB NVMe
- Virtualization
- KVM
- Network
- 10 Gbps
- Transfer
- 2.05 TB
- Port 25
- Unknown
- Monthly price at test time
- $12.00
- Hourly price at test time
- $0.017
- YABS version
- v2026-09-20
- Ran at
- Oct 16, 2026, 22:03:26 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 16, 2026, 22:01:00 UTC
- First update from the server
- Oct 16, 2026, 22:03:03 UTC
- Completed
- Oct 16, 2026, 23:35:26 UTC
- Server deleted
- Oct 16, 2026, 23:35:26 UTC
- Cost of this run
- $0.026
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading output.
This party closed at . It's read only now.
Reconnecting. Hang tight.