OneProvider General Purpose 03d40c2
Server
-
ProviderOneProvider
-
PlanGeneral Purpose 03d40c2
-
LocationMexico City, MX
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
Network1 Gbps
-
OS image1194
-
TriggerScheduled
-
Queued atOct 15, 2026, 08:03:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,516 | 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,591
|
Single-core only |
| Navigation |
1,490
|
Single-core only |
| HTML5 Browser |
1,427
|
Single-core only |
| PDF Viewer |
1,618
|
Single-core only |
| Photo Library |
1,440
|
Single-core only |
| Clang |
1,240
|
Single-core only |
| Text Processing |
1,304
|
Single-core only |
| Asset Compression |
1,543
|
Single-core only |
| HDR |
1,543
|
Single-core only |
| Photo Editor |
1,763
|
Single-core only |
| Ray Tracer |
1,562
|
Single-core only |
| Structure from Motion |
1,634
|
Single-core only |
| Game Physics |
1,510
|
Single-core only |
| Video Encoder |
1,469
|
Single-core only |
| Audio Encoder |
1,613
|
Single-core only |
| Video Player |
1,590
|
Single-core only |
Rank among the 191 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 | 47.2 GB/s | 3 | 11.9% |
| Scale higher is better | 33.3 GB/s | 3 | 6.46% |
| Add higher is better | 38.6 GB/s | 3 | 12.2% |
| Triad higher is better | 38.1 GB/s | 3 | 13.9% |
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 | 483/s | 3 | 1.49% |
| RSA 4096 verifies higher is better | 29,041/s | 3 | 21.4% |
| SHA-256 higher is better | 1.73 GB/s | 3 | 0.732% |
| AES-256-GCM higher is better | 8.49 GB/s | 3 | 0.664% |
| ChaCha20-Poly1305 higher is better | 4.98 GB/s | 3 | 1.04% |
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.18 ms | 3 | 0.585% |
| Requests per second, 90th percentile higher is better | 471/s | 3 | 0.766% |
| Request latency, 99.9th percentile lower is better | 8.32 ms | 3 | 7.89% |
| Requests per second, average higher is better | 464/s | 3 | 0.809% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 157 MB/s (40,180 IOPS) | 157.4 MB/s (40,286 IOPS) | 314.3 MB/s (80,466 IOPS) |
| 64K | 874 MB/s (13,984 IOPS) | 878.6 MB/s (14,058 IOPS) | 1.71 GB/s (28,042 IOPS) |
| 512K | 605.6 MB/s (1,211 IOPS) | 637.8 MB/s (1,275 IOPS) | 1.21 GB/s (2,486 IOPS) |
| 1M | 586.9 MB/s (586 IOPS) | 626 MB/s (625 IOPS) | 1.18 GB/s (1,211 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 | 468 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.33 Gbps | 665 Mbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 704 Mbps | 812 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.67 Gbps | 3.27 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 3.09 Gbps | 3.97 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 | 4,886 | 0.205 ms |
| fdatasync | 4,706 | 0.213 ms |
| fsync | 3,437 | 0.291 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 3,273 | 0.306 ms |
| Two 8 kB writes | ||
| open_datasync | 2,426 | 0.412 ms |
| fdatasync | 4,124 | 0.243 ms |
| fsync | 2,903 | 0.344 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,733 | 0.577 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 3,242 | 0.308 ms |
| 2 * 8kB open_sync writes | 1,609 | 0.622 ms |
| 4 * 4kB open_sync writes | 907 | 1.1 ms |
| 8 * 2kB open_sync writes | 427 | 2.34 ms |
| 16 * 1kB open_sync writes | 244 | 4.1 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 3,452 | 0.29 ms |
| write, close, fsync | 3,237 | 0.309 ms |
| Non-synced 8 kB writes | ||
| write | 721,483 | 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 | 1,656 | 0.582 ms | 0.744 ms | 0.918 ms | 4.27 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,183 | 1.74 ms | 3.09 ms | 4.6 ms | 7.96 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,170 | 6.02 ms | 17.8 ms | 28.9 ms | 56.5 ms | 0 |
| Read only | 1 | 19,182 | 0.049 ms | 0.073 ms | 0.104 ms | 0.206 ms | 0 |
| Read only | 8 | 47,854 | 0.146 ms | 0.258 ms | 0.337 ms | 0.613 ms | 0 |
| Read only | 32 | 51,084 | 0.497 ms | 0.891 ms | 1.25 ms | 2.25 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.79 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,309 | 0.725 ms | 0.935 ms | 2.09 ms | 5.23 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,424 | 2.11 ms | 4.09 ms | 6.92 ms | 12.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,193 | 6.91 ms | 12.7 ms | 19.4 ms | 35.9 ms | 0 |
| Read only | 1 | 8,584 | 0.122 ms | 0.194 ms | 0.301 ms | 1.16 ms | 0 |
| Read only | 8 | 29,626 | 0.226 ms | 0.51 ms | 0.729 ms | 2.43 ms | 0 |
| Read only | 32 | 32,132 | 0.828 ms | 1.68 ms | 2.63 ms | 4.72 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 18.5 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 | 357 | 7,134 | 2.48 ms | 3.36 ms | 13.2 ms | 0 |
| Read/write | 8 | 760 | 15,198 | 9.56 ms | 21.1 ms | 29.7 ms | 0 |
| Read/write | 32 | 801 | 16,027 | 39.7 ms | 66.8 ms | 87.6 ms | 0 |
| Read only | 1 | 867 | 13,875 | 1.12 ms | 1.44 ms | 1.67 ms | 0 |
| Read only | 8 | 1,550 | 24,807 | 4.91 ms | 7.17 ms | 8.43 ms | 0 |
| Read only | 32 | 1,455 | 23,283 | 21.5 ms | 28.2 ms | 32.5 ms | 0 |
10 tables of 100,000 rows, loaded in 8.1 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 66,952 | 60,865 | 0.511 ms | 3.23 ms | 4.8 ms |
| 1:1 set:get | 66,390 | 33,195 | 0.503 ms | 3.25 ms | 4.8 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 | 661 | 2,340 | 3,401 | 660 ms |
| Express express-postgresjs | 7,534 | 10,662 | 27,197 | 62.9 ms |
| Fastify fastify-postgres | 7,267 | 11,321 | 30,456 | 80.9 ms |
| NestJS nestjs | 4,855 | 5,586 | 16,512 | 96 ms |
| Nuxt nuxt | 6,778 | 10,464 | 29,949 | 78.9 ms |
| FastAPI fastapi | 3,923 | 4,582 | 18,381 | 237 ms |
| Django django-postgresql | 1,241 | 1,600 | 3,518 | 315 ms |
| Rails rails | 2,329 | 3,196 | 12,056 | 142 ms |
| Laravel laravel | 799 | 884 | 1,603 | 371 ms |
| Symfony symfony | 1,066 | 1,189 | 3,104 | 266 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.44 | 655 ms | 752 ms | 786 ms | 0% |
| Shop page | 2.44 | 889 ms | 991 ms | 1.04 s | 0% |
| Category page | 2.44 | 548 ms | 927 ms | 967 ms | 0% |
| Product page | 2.44 | 600 ms | 678 ms | 721 ms | 0% |
| Product search | 2.44 | 527 ms | 598 ms | 626 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.47 | 2.34 s | 2.62 s | 2.71 s | 0% |
| Shop page | 2.47 | 3.15 s | 3.65 s | 3.72 s | 0% |
| Category page | 2.47 | 2.8 s | 3.38 s | 3.61 s | 0% |
| Product page | 2.47 | 2.32 s | 2.49 s | 2.56 s | 0% |
| Product search | 2.47 | 2.19 s | 2.35 s | 2.41 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.74 | 700 ms | 773 ms | 827 ms | 0% |
| Cart | 4.74 | 549 ms | 624 ms | 689 ms | 0% |
| Checkout | 4.74 | 429 ms | 480 ms | 516 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.8 | 2.28 s | 2.78 s | 2.92 s | 0% |
| Cart | 4.8 | 2.4 s | 2.72 s | 2.83 s | 0% |
| Checkout | 4.8 | 1.86 s | 2.17 s | 2.26 s | 0% |
k6 with a fixed number of virtual users, 61 to 66 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.64 | 169 ms | 208 ms | 386 ms | 0% |
| Topic JSON | 1.32 | 86.6 ms | 97.8 ms | 127 ms | 0% |
| Home page | 1.32 | 150 ms | 173 ms | 342 ms | 0% |
| Categories page | 0.661 | 177 ms | 206 ms | 337 ms | 0% |
| User activity page | 0.661 | 106 ms | 124 ms | 135 ms | 0% |
| 4 virtual users | |||||
| Topic page | 4.53 | 387 ms | 545 ms | 1.06 s | 0% |
| Topic JSON | 2.28 | 202 ms | 264 ms | 389 ms | 0% |
| Home page | 2.25 | 353 ms | 548 ms | 798 ms | 0% |
| Categories page | 1.16 | 384 ms | 551 ms | 649 ms | 0% |
| User activity page | 1.12 | 263 ms | 386 ms | 561 ms | 0% |
| 16 virtual users | |||||
| Topic page | 4.56 | 1.4 s | 1.66 s | 1.85 s | 0% |
| Topic JSON | 2.29 | 1.23 s | 1.49 s | 1.71 s | 0% |
| Home page | 2.24 | 1.36 s | 1.62 s | 1.9 s | 0% |
| Categories page | 1.17 | 1.42 s | 1.6 s | 1.71 s | 0% |
| User activity page | 1.14 | 1.26 s | 1.47 s | 1.68 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 93 | 49.6 ms | 115 ms | 153 ms | 0% |
| Topic JSON | 46.5 | 48 ms | 116 ms | 151 ms | 0% |
| Home page | 46.5 | 48.8 ms | 117 ms | 150 ms | 0% |
| Categories page | 23.2 | 48.9 ms | 113 ms | 149 ms | 0% |
| User activity page | 23.3 | 153 ms | 251 ms | 358 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 489 MB of it. The container peaked at 1,489 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 9.93 | 28.2 ms | 33.7 ms | 50.1 ms | 0% |
| Post page | 24.8 | 15 ms | 19.3 ms | 27.5 ms | 0% |
| Tag page | 4.96 | 19.7 ms | 23.8 ms | 29.5 ms | 0% |
| Author page | 4.96 | 19.2 ms | 23.4 ms | 29.7 ms | 0% |
| RSS feed | 4.95 | 23.8 ms | 28.7 ms | 42.6 ms | 0% |
| 4 virtual users | |||||
| Home page | 12 | 85.7 ms | 115 ms | 149 ms | 0% |
| Post page | 29.9 | 62 ms | 88.3 ms | 113 ms | 0% |
| Tag page | 5.98 | 54.7 ms | 81.6 ms | 97.2 ms | 0% |
| Author page | 5.96 | 55.4 ms | 78.5 ms | 91.1 ms | 0% |
| RSS feed | 5.96 | 61.4 ms | 91.4 ms | 118 ms | 0% |
| 16 virtual users | |||||
| Home page | 11.7 | 348 ms | 436 ms | 466 ms | 0% |
| Post page | 29.2 | 286 ms | 366 ms | 400 ms | 0% |
| Tag page | 5.85 | 191 ms | 257 ms | 294 ms | 0% |
| Author page | 5.83 | 188 ms | 254 ms | 273 ms | 0% |
| RSS feed | 5.83 | 195 ms | 254 ms | 296 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.44 | 27.8 ms | 37.7 ms | 57 ms | 0% |
| Post editor | 16.3 | 10.4 ms | 13.7 ms | 23.4 ms | 0% |
| Saving a draft | 16.3 | 26.4 ms | 32.5 ms | 40.9 ms | 0% |
| Member list | 5.44 | 33.5 ms | 41.4 ms | 59.7 ms | 0% |
| 4 virtual users | |||||
| Post list | 6.71 | 37.4 ms | 48.5 ms | 82 ms | 0% |
| Post editor | 20.2 | 18.4 ms | 25 ms | 38.2 ms | 0% |
| Saving a draft | 20.2 | 145 ms | 192 ms | 233 ms | 0% |
| Member list | 6.74 | 42.1 ms | 51.6 ms | 81.1 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 361 MB and MySQL at 585 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.91 | 70.4 ms | 80.8 ms | 83.3 ms | 0% |
| Blog index | 1.9 | 233 ms | 251 ms | 261 ms | 0% |
| Blog post | 5.69 | 22.6 ms | 33.3 ms | 42 ms | 0% |
| Bread page | 5.69 | 24.9 ms | 28.7 ms | 31.4 ms | 0% |
| Location page | 1.9 | 23.9 ms | 27.7 ms | 32.7 ms | 0% |
| Site search | 1.9 | 40 ms | 64.4 ms | 67.1 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.96 | 189 ms | 264 ms | 330 ms | 0% |
| Blog index | 3.01 | 639 ms | 847 ms | 904 ms | 0% |
| Blog post | 8.89 | 55.1 ms | 92.2 ms | 117 ms | 0% |
| Bread page | 8.94 | 59.9 ms | 87.8 ms | 101 ms | 0% |
| Location page | 3.01 | 57.9 ms | 86.9 ms | 112 ms | 0% |
| Site search | 2.95 | 84 ms | 189 ms | 215 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.82 | 676 ms | 942 ms | 1.04 s | 0% |
| Blog index | 2.89 | 1.66 s | 2.1 s | 2.24 s | 0% |
| Blog post | 8.46 | 358 ms | 604 ms | 831 ms | 0% |
| Bread page | 8.52 | 374 ms | 653 ms | 860 ms | 0% |
| Location page | 2.84 | 347 ms | 607 ms | 748 ms | 0% |
| Site search | 2.79 | 429 ms | 735 ms | 862 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.759 | 74 ms | 88.4 ms | 95.3 ms | 0% |
| Page explorer | 1.55 | 312 ms | 381 ms | 452 ms | 0% |
| Page editor | 2.29 | 147 ms | 177 ms | 269 ms | 0% |
| Image library | 0.759 | 55.6 ms | 62.6 ms | 452 ms | 0% |
| Admin page search | 0.759 | 31 ms | 69 ms | 72 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.2 | 187 ms | 490 ms | 560 ms | 0% |
| Page explorer | 2.44 | 805 ms | 1.21 s | 1.44 s | 0% |
| Page editor | 3.65 | 366 ms | 671 ms | 936 ms | 0% |
| Image library | 1.22 | 186 ms | 474 ms | 568 ms | 0% |
| Admin page search | 1.2 | 78.1 ms | 265 ms | 316 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 297 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0.2% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 40 GB SSD | 39.3 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
- 2850 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 1.9 GiB
- Swap reported
- 512 MiB
- Disk reported
- 39.3 GiB
- Virtualization reported
- KVM
- CPU steal
- 0.2% 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 03d40c2
- Product line
- General Purpose
- Location
- Mexico City, MX
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 40 GB SSD
- Virtualization
- KVM
- Network
- 1 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 15, 2026, 08:05:30 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 15, 2026, 08:03:00 UTC
- First update from the server
- Oct 15, 2026, 08:05:27 UTC
- Completed
- Oct 15, 2026, 09:35:05 UTC
- Server deleted
- Oct 15, 2026, 09:35:05 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.