OneProvider General Purpose GP1.2-2-40-PRO
Server
-
ProviderOneProvider
-
PlanGeneral Purpose GP1.2-2-40-PRO
-
LocationSeattle, US
-
vCPU2
-
RAM2 GB
-
Storage40 GB NVMe
-
Network10 Gbps
-
OS image1194
-
TriggerScheduled
-
Queued atOct 17, 2026, 08:43:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,225 | 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,194
|
Single-core only |
| Navigation |
1,320
|
Single-core only |
| HTML5 Browser |
1,206
|
Single-core only |
| PDF Viewer |
1,239
|
Single-core only |
| Photo Library |
1,104
|
Single-core only |
| Clang |
1,162
|
Single-core only |
| Text Processing |
1,074
|
Single-core only |
| Asset Compression |
1,205
|
Single-core only |
| HDR |
1,285
|
Single-core only |
| Photo Editor |
1,410
|
Single-core only |
| Ray Tracer |
1,242
|
Single-core only |
| Structure from Motion |
1,313
|
Single-core only |
| Game Physics |
1,284
|
Single-core only |
| Video Encoder |
1,192
|
Single-core only |
| Audio Encoder |
1,234
|
Single-core only |
| Video Player |
1,181
|
Single-core only |
Rank among the 241 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 | 64.1 GB/s | 3 | 1.09% |
| Scale higher is better | 66.4 GB/s | 3 | 1.92% |
| Add higher is better | 71.7 GB/s | 3 | 2.4% |
| Triad higher is better | 73.4 GB/s | 3 | 1.87% |
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 | 385/s | 3 | 0.105% |
| RSA 4096 verifies higher is better | 24,809/s | 3 | 0.458% |
| SHA-256 higher is better | 1.37 GB/s | 3 | 0.0289% |
| AES-256-GCM higher is better | 6.32 GB/s | 3 | 1.06% |
| ChaCha20-Poly1305 higher is better | 3.59 GB/s | 3 | 0.0202% |
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 | 344/s | 3 | 0.168% |
| Request latency, 99.9th percentile lower is better | 30.4 ms | 3 | 0.919% |
| Requests per second, average higher is better | 342/s | 3 | 0.161% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 40.3 MB/s (10,310 IOPS) | 40.4 MB/s (10,331 IOPS) | 80.6 MB/s (20,641 IOPS) |
| 64K | 518.8 MB/s (8,301 IOPS) | 521.6 MB/s (8,344 IOPS) | 1.02 GB/s (16,645 IOPS) |
| 512K | 2.09 GB/s (4,281 IOPS) | 2.2 GB/s (4,508 IOPS) | 4.29 GB/s (8,789 IOPS) |
| 1M | 2.62 GB/s (2,678 IOPS) | 2.79 GB/s (2,856 IOPS) | 5.41 GB/s (5,534 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 | 988 Mbps | 1.49 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.05 Gbps | 1.64 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 722 Mbps | 1.18 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 2.61 Gbps | 3.22 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.35 Gbps | 3.54 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 | 3,060 | 0.327 ms |
| fdatasync | 2,993 | 0.334 ms |
| fsync | 1,863 | 0.537 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,943 | 0.515 ms |
| Two 8 kB writes | ||
| open_datasync | 1,565 | 0.639 ms |
| fdatasync | 3,003 | 0.333 ms |
| fsync | 1,846 | 0.542 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 982 | 1.02 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 1,923 | 0.52 ms |
| 2 * 8kB open_sync writes | 972 | 1.03 ms |
| 4 * 4kB open_sync writes | 490 | 2.04 ms |
| 8 * 2kB open_sync writes | 217 | 4.6 ms |
| 16 * 1kB open_sync writes | 104 | 9.66 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 1,804 | 0.554 ms |
| write, close, fsync | 1,819 | 0.55 ms |
| Non-synced 8 kB writes | ||
| write | 530,839 | 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,489 | 0.608 ms | 0.798 ms | 1.27 ms | 15.5 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,504 | 1.56 ms | 3.61 ms | 25.1 ms | 27.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,854 | 4.85 ms | 31 ms | 45.7 ms | 71.9 ms | 0 |
| Read only | 1 | 21,830 | 0.036 ms | 0.049 ms | 0.066 ms | 0.246 ms | 0 |
| Read only | 8 | 49,096 | 0.098 ms | 0.183 ms | 0.308 ms | 24.3 ms | 0 |
| Read only | 32 | 50,858 | 0.186 ms | 1.06 ms | 6.07 ms | 33.1 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.33 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 | 1,014 | 0.861 ms | 1.1 ms | 3.72 ms | 23.9 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,697 | 1.96 ms | 5.25 ms | 26.4 ms | 63.3 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,404 | 5.56 ms | 31.6 ms | 60.9 ms | 76.5 ms | 0 |
| Read only | 1 | 5,224 | 0.173 ms | 0.254 ms | 0.871 ms | 22.6 ms | 0 |
| Read only | 8 | 25,780 | 0.169 ms | 0.51 ms | 1.34 ms | 25.4 ms | 0 |
| Read only | 32 | 29,789 | 0.35 ms | 2.34 ms | 14.9 ms | 41.8 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 14.4 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 | 328 | 6,555 | 2.81 ms | 4.03 ms | 9.22 ms | 0 |
| Read/write | 8 | 721 | 14,426 | 8.28 ms | 32.5 ms | 38.2 ms | 0 |
| Read/write | 32 | 786 | 15,715 | 33.7 ms | 87.6 ms | 123 ms | 0 |
| Read only | 1 | 799 | 12,784 | 0.937 ms | 1.21 ms | 23.9 ms | 0 |
| Read only | 8 | 1,569 | 25,107 | 3.36 ms | 25.3 ms | 45 ms | 0 |
| Read only | 32 | 1,391 | 22,264 | 16.1 ms | 52.9 ms | 150 ms | 0 |
10 tables of 100,000 rows, loaded in 7.7 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 54,368 | 49,425 | 0.447 ms | 20.4 ms | 29.2 ms |
| 1:1 set:get | 53,177 | 26,588 | 0.447 ms | 20.7 ms | 28.9 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 | 600 | 2,037 | 3,099 | 674 ms |
| Express express-postgresjs | 5,878 | 9,212 | 32,585 | 87.9 ms |
| Fastify fastify-postgres | 5,819 | 8,922 | 36,057 | 94.3 ms |
| NestJS nestjs | 4,652 | 5,210 | 19,024 | 104 ms |
| Nuxt nuxt | 5,299 | 9,102 | 34,660 | 100 ms |
| FastAPI fastapi | 3,403 | 4,292 | 21,694 | 434 ms |
| Django django-postgresql | 1,345 | 1,510 | 3,363 | 396 ms |
| Rails rails | 2,304 | 3,011 | 12,091 | 154 ms |
| Laravel laravel | 745 | 798 | 1,464 | 378 ms |
| Symfony symfony | 934 | 1,031 | 2,892 | 304 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.28 | 698 ms | 924 ms | 1.15 s | 0% |
| Shop page | 2.28 | 915 ms | 1.2 s | 1.31 s | 0% |
| Category page | 2.28 | 589 ms | 970 ms | 1.1 s | 0% |
| Product page | 2.28 | 639 ms | 913 ms | 963 ms | 0% |
| Product search | 2.28 | 556 ms | 797 ms | 866 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.27 | 2.55 s | 2.95 s | 3.05 s | 0% |
| Shop page | 2.27 | 3.39 s | 3.91 s | 4.16 s | 0% |
| Category page | 2.27 | 3.04 s | 3.64 s | 3.78 s | 0% |
| Product page | 2.27 | 2.6 s | 2.85 s | 2.91 s | 0% |
| Product search | 2.27 | 2.41 s | 2.69 s | 2.83 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.36 | 745 ms | 994 ms | 1.07 s | 0% |
| Cart | 4.36 | 584 ms | 813 ms | 885 ms | 0% |
| Checkout | 4.36 | 458 ms | 677 ms | 756 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.36 | 2.51 s | 3.04 s | 3.18 s | 0% |
| Cart | 4.36 | 2.61 s | 2.98 s | 3.09 s | 0% |
| Checkout | 4.36 | 2.11 s | 2.4 s | 2.54 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.73 | 158 ms | 207 ms | 479 ms | 0% |
| Topic JSON | 1.37 | 79.1 ms | 114 ms | 141 ms | 0% |
| Home page | 1.37 | 141 ms | 283 ms | 432 ms | 0% |
| Categories page | 0.695 | 164 ms | 207 ms | 318 ms | 0% |
| User activity page | 0.678 | 97 ms | 140 ms | 147 ms | 0% |
| 4 virtual users | |||||
| Topic page | 3.65 | 479 ms | 675 ms | 1.17 s | 0% |
| Topic JSON | 1.81 | 238 ms | 342 ms | 383 ms | 0% |
| Home page | 1.8 | 418 ms | 663 ms | 1.21 s | 0% |
| Categories page | 0.924 | 515 ms | 679 ms | 746 ms | 0% |
| User activity page | 0.924 | 328 ms | 532 ms | 746 ms | 0% |
| 16 virtual users | |||||
| Topic page | 3.98 | 1.55 s | 2.07 s | 2.38 s | 0% |
| Topic JSON | 1.98 | 1.31 s | 1.79 s | 1.95 s | 0% |
| Home page | 1.99 | 1.51 s | 1.81 s | 2 s | 0% |
| Categories page | 1 | 1.58 s | 1.91 s | 2.02 s | 0% |
| User activity page | 1 | 1.38 s | 1.84 s | 1.95 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 82.4 | 60 ms | 128 ms | 176 ms | 0% |
| Topic JSON | 41.2 | 60.3 ms | 124 ms | 176 ms | 0% |
| Home page | 41.2 | 62.3 ms | 130 ms | 171 ms | 0% |
| Categories page | 20.6 | 58.5 ms | 118 ms | 167 ms | 0% |
| User activity page | 20.6 | 179 ms | 277 ms | 388 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 491 MB of it. The container peaked at 1,515 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 9.43 | 27.6 ms | 48.9 ms | 63.7 ms | 0% |
| Post page | 23.5 | 12.7 ms | 32.5 ms | 37.1 ms | 0% |
| Tag page | 4.71 | 17.4 ms | 36.5 ms | 41.2 ms | 0% |
| Author page | 4.7 | 18.2 ms | 38 ms | 50 ms | 0% |
| RSS feed | 4.7 | 22 ms | 41.9 ms | 44.2 ms | 0% |
| 4 virtual users | |||||
| Home page | 10.4 | 103 ms | 145 ms | 189 ms | 0% |
| Post page | 26 | 72 ms | 101 ms | 159 ms | 0% |
| Tag page | 5.19 | 63 ms | 88.8 ms | 103 ms | 0% |
| Author page | 5.19 | 67.5 ms | 98 ms | 140 ms | 0% |
| RSS feed | 5.19 | 72.2 ms | 102 ms | 143 ms | 0% |
| 16 virtual users | |||||
| Home page | 10.8 | 375 ms | 478 ms | 498 ms | 0% |
| Post page | 27 | 306 ms | 399 ms | 444 ms | 0% |
| Tag page | 5.41 | 205 ms | 296 ms | 325 ms | 0% |
| Author page | 5.39 | 203 ms | 290 ms | 318 ms | 0% |
| RSS feed | 5.39 | 210 ms | 296 ms | 328 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.4 | 25.8 ms | 43.7 ms | 70.6 ms | 0% |
| Post editor | 16.2 | 8.93 ms | 24.4 ms | 30.2 ms | 0% |
| Saving a draft | 16.2 | 24.3 ms | 44.4 ms | 52.1 ms | 0% |
| Member list | 5.42 | 28.9 ms | 46.1 ms | 55.4 ms | 0% |
| 4 virtual users | |||||
| Post list | 5.98 | 37.1 ms | 62.5 ms | 101 ms | 0% |
| Post editor | 17.9 | 15.2 ms | 40.3 ms | 50.4 ms | 0% |
| Saving a draft | 18 | 168 ms | 229 ms | 284 ms | 0% |
| Member list | 5.98 | 40.9 ms | 65.9 ms | 85.3 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 356 MB and MySQL at 587 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 2.03 | 59.8 ms | 75.8 ms | 79.7 ms | 0% |
| Blog index | 2.03 | 240 ms | 256 ms | 339 ms | 0% |
| Blog post | 6.07 | 19.4 ms | 30.7 ms | 42.2 ms | 0% |
| Bread page | 6.07 | 21.3 ms | 25.7 ms | 37.2 ms | 0% |
| Location page | 2.03 | 20.3 ms | 24.2 ms | 26.3 ms | 0% |
| Site search | 2.01 | 36.3 ms | 58 ms | 71.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.88 | 200 ms | 259 ms | 272 ms | 0% |
| Blog index | 2.91 | 691 ms | 850 ms | 882 ms | 0% |
| Blog post | 8.63 | 55.6 ms | 91.9 ms | 122 ms | 0% |
| Bread page | 8.67 | 60.4 ms | 89.7 ms | 102 ms | 0% |
| Location page | 2.91 | 58.1 ms | 86.9 ms | 101 ms | 0% |
| Site search | 2.86 | 86.7 ms | 170 ms | 200 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.69 | 651 ms | 914 ms | 1.02 s | 0% |
| Blog index | 2.8 | 1.77 s | 2.11 s | 2.27 s | 0% |
| Blog post | 8.14 | 374 ms | 682 ms | 753 ms | 0% |
| Bread page | 8.19 | 374 ms | 649 ms | 731 ms | 0% |
| Location page | 2.75 | 366 ms | 659 ms | 729 ms | 0% |
| Site search | 2.72 | 472 ms | 761 ms | 868 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.793 | 62.3 ms | 83 ms | 171 ms | 0% |
| Page explorer | 1.62 | 306 ms | 340 ms | 438 ms | 0% |
| Page editor | 2.4 | 136 ms | 192 ms | 279 ms | 0% |
| Image library | 0.793 | 48.1 ms | 76 ms | 587 ms | 0% |
| Admin page search | 0.793 | 25.7 ms | 67.5 ms | 124 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.25 | 253 ms | 431 ms | 496 ms | 0% |
| Page explorer | 2.55 | 751 ms | 1.07 s | 1.23 s | 0% |
| Page editor | 3.82 | 337 ms | 589 ms | 708 ms | 0% |
| Image library | 1.27 | 209 ms | 369 ms | 500 ms | 0% |
| Admin page search | 1.25 | 88.5 ms | 260 ms | 380 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 176 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-PRO
- 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
- 3.07 TB
- Port 25
- Unknown
- Monthly price at test time
- $14.00
- Hourly price at test time
- $0.019
- YABS version
- v2026-09-20
- Ran at
- Oct 17, 2026, 08:45:08 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 17, 2026, 08:43:00 UTC
- Server created
- Oct 17, 2026, 08:45:05 UTC
- First update from the server
- Oct 17, 2026, 08:45:05 UTC
- Completed
- Oct 17, 2026, 10:16:19 UTC
- Server deleted
- Oct 17, 2026, 10:16:19 UTC
- Cost of this run
- $0.030
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.