OneProvider General Purpose 03d80c2
Server
-
ProviderOneProvider
-
PlanGeneral Purpose 03d80c2
-
LocationMexico City, MX
-
vCPU2
-
RAM2 GB
-
Storage80 GB SSD
-
Network1 Gbps
-
OS image1194
-
TriggerScheduled
-
Queued atOct 18, 2026, 00:46:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,551 | 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,651
|
Single-core only |
| Navigation |
1,592
|
Single-core only |
| HTML5 Browser |
1,455
|
Single-core only |
| PDF Viewer |
1,637
|
Single-core only |
| Photo Library |
1,449
|
Single-core only |
| Clang |
1,316
|
Single-core only |
| Text Processing |
1,426
|
Single-core only |
| Asset Compression |
1,631
|
Single-core only |
| HDR |
1,570
|
Single-core only |
| Photo Editor |
1,815
|
Single-core only |
| Ray Tracer |
1,548
|
Single-core only |
| Structure from Motion |
1,725
|
Single-core only |
| Game Physics |
1,485
|
Single-core only |
| Video Encoder |
1,446
|
Single-core only |
| Audio Encoder |
1,529
|
Single-core only |
| Video Player |
1,622
|
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 | 47.9 GB/s | 3 | 12.6% |
| Scale higher is better | 32.7 GB/s | 3 | 3.7% |
| Add higher is better | 36.9 GB/s | 3 | 6.45% |
| Triad higher is better | 38 GB/s | 3 | 10.8% |
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 | 492/s | 3 | 2.07% |
| RSA 4096 verifies higher is better | 32,535/s | 3 | 0.975% |
| SHA-256 higher is better | 1.77 GB/s | 3 | 1.57% |
| AES-256-GCM higher is better | 8.74 GB/s | 3 | 0.732% |
| ChaCha20-Poly1305 higher is better | 5.04 GB/s | 3 | 1.49% |
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.24 ms | 3 | 4.69% |
| Requests per second, 90th percentile higher is better | 463/s | 3 | 5.81% |
| Request latency, 99.9th percentile lower is better | 8.21 ms | 3 | 15.9% |
| Requests per second, average higher is better | 454/s | 3 | 6.58% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 82.5 MB/s (21,125 IOPS) | 82.7 MB/s (21,181 IOPS) | 165.3 MB/s (42,306 IOPS) |
| 64K | 1.29 GB/s (21,057 IOPS) | 1.29 GB/s (21,168 IOPS) | 2.58 GB/s (42,225 IOPS) |
| 512K | 1.08 GB/s (2,203 IOPS) | 1.13 GB/s (2,320 IOPS) | 2.21 GB/s (4,523 IOPS) |
| 1M | 999 MB/s (998 IOPS) | 1.04 GB/s (1,065 IOPS) | 2.02 GB/s (2,063 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 | 1.31 Gbps | 568 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.32 Gbps | 631 Mbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 598 Mbps | 728 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 2 Gbps | 2.23 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 3.34 Gbps | 3.07 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 | 5,162 | 0.194 ms |
| fdatasync | 5,073 | 0.197 ms |
| fsync | 3,356 | 0.298 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 3,668 | 0.273 ms |
| Two 8 kB writes | ||
| open_datasync | 2,707 | 0.369 ms |
| fdatasync | 4,877 | 0.205 ms |
| fsync | 3,450 | 0.29 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,966 | 0.509 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 3,696 | 0.271 ms |
| 2 * 8kB open_sync writes | 1,916 | 0.522 ms |
| 4 * 4kB open_sync writes | 890 | 1.12 ms |
| 8 * 2kB open_sync writes | 496 | 2.01 ms |
| 16 * 1kB open_sync writes | 260 | 3.84 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 3,363 | 0.297 ms |
| write, close, fsync | 3,380 | 0.296 ms |
| Non-synced 8 kB writes | ||
| write | 715,586 | 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,707 | 0.573 ms | 0.744 ms | 0.944 ms | 2.13 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,309 | 1.7 ms | 3.07 ms | 4.27 ms | 7.91 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,501 | 5.76 ms | 16 ms | 26.6 ms | 48.4 ms | 0 |
| Read only | 1 | 20,356 | 0.047 ms | 0.067 ms | 0.091 ms | 0.174 ms | 0 |
| Read only | 8 | 48,261 | 0.144 ms | 0.254 ms | 0.321 ms | 0.529 ms | 0 |
| Read only | 32 | 54,772 | 0.463 ms | 0.803 ms | 1.12 ms | 2.17 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,204 | 0.811 ms | 1.07 ms | 1.47 ms | 4.2 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,609 | 2.07 ms | 3.44 ms | 5.32 ms | 14.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,358 | 6.78 ms | 12 ms | 16.7 ms | 31.9 ms | 0 |
| Read only | 1 | 5,833 | 0.209 ms | 0.293 ms | 0.517 ms | 1.39 ms | 0 |
| Read only | 8 | 27,891 | 0.224 ms | 0.588 ms | 0.847 ms | 2.57 ms | 0 |
| Read only | 32 | 32,970 | 0.797 ms | 1.66 ms | 2.56 ms | 4.63 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 15.3 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 | 379 | 7,574 | 2.48 ms | 3.49 ms | 5.88 ms | 0 |
| Read/write | 8 | 782 | 15,631 | 9.91 ms | 15.8 ms | 20 ms | 0 |
| Read/write | 32 | 818 | 16,360 | 38.9 ms | 65.6 ms | 84.5 ms | 0 |
| Read only | 1 | 843 | 13,482 | 1.16 ms | 1.47 ms | 1.79 ms | 0 |
| Read only | 8 | 1,608 | 25,724 | 4.82 ms | 6.67 ms | 7.7 ms | 0 |
| Read only | 32 | 1,460 | 23,366 | 21.9 ms | 27.7 ms | 30.8 ms | 0 |
10 tables of 100,000 rows, loaded in 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 | 67,902 | 61,728 | 0.471 ms | 3.25 ms | 4.74 ms |
| 1:1 set:get | 66,975 | 33,487 | 0.487 ms | 3.2 ms | 4.86 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 | 674 | 2,461 | 3,639 | 546 ms |
| Express express-postgresjs | 7,616 | 11,513 | 29,239 | 65.8 ms |
| Fastify fastify-postgres | 7,764 | 11,611 | 34,911 | 62.5 ms |
| NestJS nestjs | 5,059 | 5,676 | 17,301 | 91.5 ms |
| Nuxt nuxt | 7,114 | 11,179 | 32,169 | 70.4 ms |
| FastAPI fastapi | 3,952 | 4,759 | 18,866 | 259 ms |
| Django django-postgresql | 1,399 | 1,688 | 3,647 | 414 ms |
| Rails rails | 2,357 | 3,401 | 12,636 | 166 ms |
| Laravel laravel | 840 | 877 | 1,570 | 348 ms |
| Symfony symfony | 1,103 | 1,174 | 3,279 | 249 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 | 642 ms | 721 ms | 748 ms | 0% |
| Shop page | 2.44 | 889 ms | 985 ms | 1.02 s | 0% |
| Category page | 2.44 | 560 ms | 908 ms | 954 ms | 0% |
| Product page | 2.44 | 594 ms | 669 ms | 761 ms | 0% |
| Product search | 2.44 | 519 ms | 585 ms | 629 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.45 | 2.37 s | 2.65 s | 2.69 s | 0% |
| Shop page | 2.45 | 3.14 s | 3.59 s | 3.63 s | 0% |
| Category page | 2.45 | 2.77 s | 3.36 s | 3.59 s | 0% |
| Product page | 2.45 | 2.41 s | 2.58 s | 2.69 s | 0% |
| Product search | 2.45 | 2.24 s | 2.45 s | 2.52 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.75 | 691 ms | 797 ms | 828 ms | 0% |
| Cart | 4.75 | 556 ms | 645 ms | 660 ms | 0% |
| Checkout | 4.75 | 427 ms | 502 ms | 518 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.81 | 2.28 s | 2.74 s | 2.85 s | 0% |
| Cart | 4.81 | 2.38 s | 2.65 s | 2.72 s | 0% |
| Checkout | 4.81 | 1.87 s | 2.14 s | 2.24 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.28 | 191 ms | 261 ms | 388 ms | 0% |
| Topic JSON | 1.16 | 97.9 ms | 137 ms | 183 ms | 0% |
| Home page | 1.16 | 175 ms | 350 ms | 462 ms | 0% |
| Categories page | 0.579 | 199 ms | 284 ms | 424 ms | 0% |
| User activity page | 0.563 | 111 ms | 189 ms | 263 ms | 0% |
| 4 virtual users | |||||
| Topic page | 4.54 | 390 ms | 610 ms | 934 ms | 0% |
| Topic JSON | 2.26 | 203 ms | 268 ms | 450 ms | 0% |
| Home page | 2.28 | 341 ms | 519 ms | 861 ms | 0% |
| Categories page | 1.14 | 402 ms | 524 ms | 733 ms | 0% |
| User activity page | 1.14 | 233 ms | 394 ms | 653 ms | 0% |
| 16 virtual users | |||||
| Topic page | 4.38 | 1.44 s | 1.87 s | 2 s | 0% |
| Topic JSON | 2.21 | 1.27 s | 1.59 s | 1.78 s | 0% |
| Home page | 2.2 | 1.4 s | 1.81 s | 2.2 s | 0% |
| Categories page | 1.11 | 1.48 s | 1.79 s | 1.91 s | 0% |
| User activity page | 1.07 | 1.29 s | 1.6 s | 1.65 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 90.3 | 48.3 ms | 127 ms | 167 ms | 0% |
| Topic JSON | 45.2 | 45.4 ms | 123 ms | 159 ms | 0% |
| Home page | 45.1 | 49.1 ms | 129 ms | 168 ms | 0% |
| Categories page | 22.6 | 43 ms | 115 ms | 160 ms | 0% |
| User activity page | 22.6 | 163 ms | 272 ms | 368 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 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 392 MB of it. The container peaked at 1,476 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 10.3 | 27.5 ms | 32.5 ms | 41.7 ms | 0% |
| Post page | 25.6 | 14.4 ms | 18.4 ms | 28.4 ms | 0% |
| Tag page | 5.13 | 19.1 ms | 23.7 ms | 41.9 ms | 0% |
| Author page | 5.11 | 18.8 ms | 21.8 ms | 24.4 ms | 0% |
| RSS feed | 5.11 | 23.4 ms | 27.7 ms | 31.1 ms | 0% |
| 4 virtual users | |||||
| Home page | 12.1 | 86.1 ms | 114 ms | 136 ms | 0% |
| Post page | 30.2 | 60.4 ms | 90.5 ms | 117 ms | 0% |
| Tag page | 6.04 | 54.3 ms | 74.6 ms | 103 ms | 0% |
| Author page | 6.06 | 55.3 ms | 77.4 ms | 113 ms | 0% |
| RSS feed | 6.01 | 60.6 ms | 83 ms | 102 ms | 0% |
| 16 virtual users | |||||
| Home page | 12.1 | 330 ms | 411 ms | 450 ms | 0% |
| Post page | 30.2 | 278 ms | 350 ms | 382 ms | 0% |
| Tag page | 6.07 | 180 ms | 236 ms | 264 ms | 0% |
| Author page | 6.04 | 180 ms | 241 ms | 278 ms | 0% |
| RSS feed | 6.02 | 184 ms | 249 ms | 291 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.78 | 26.3 ms | 33.4 ms | 47.2 ms | 0% |
| Post editor | 17.4 | 9.8 ms | 12.8 ms | 18.7 ms | 0% |
| Saving a draft | 17.4 | 24.7 ms | 30.6 ms | 39.2 ms | 0% |
| Member list | 5.8 | 32 ms | 39 ms | 45 ms | 0% |
| 4 virtual users | |||||
| Post list | 7.08 | 36.1 ms | 48.7 ms | 76.6 ms | 0% |
| Post editor | 21.3 | 17 ms | 22.6 ms | 38.6 ms | 0% |
| Saving a draft | 21.4 | 143 ms | 183 ms | 226 ms | 0% |
| Member list | 7.13 | 41.4 ms | 50.1 ms | 85.4 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 360 MB and MySQL at 590 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.99 | 66.7 ms | 72.5 ms | 76.8 ms | 0% |
| Blog index | 1.99 | 223 ms | 235 ms | 240 ms | 0% |
| Blog post | 5.94 | 21.7 ms | 33.2 ms | 35.1 ms | 0% |
| Bread page | 5.96 | 23.9 ms | 26.2 ms | 28.1 ms | 0% |
| Location page | 1.99 | 23 ms | 26.3 ms | 29.4 ms | 0% |
| Site search | 1.98 | 38.3 ms | 60.6 ms | 64.1 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.99 | 188 ms | 254 ms | 276 ms | 0% |
| Blog index | 3.04 | 645 ms | 889 ms | 950 ms | 0% |
| Blog post | 8.98 | 54.1 ms | 90.8 ms | 119 ms | 0% |
| Bread page | 9.02 | 59.4 ms | 86.6 ms | 95.8 ms | 0% |
| Location page | 3.04 | 56.7 ms | 86.2 ms | 120 ms | 0% |
| Site search | 2.99 | 84.1 ms | 174 ms | 209 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.72 | 671 ms | 909 ms | 955 ms | 0% |
| Blog index | 2.8 | 1.76 s | 2.12 s | 2.23 s | 0% |
| Blog post | 8.1 | 382 ms | 601 ms | 686 ms | 0% |
| Bread page | 8.17 | 399 ms | 604 ms | 719 ms | 0% |
| Location page | 2.74 | 381 ms | 586 ms | 670 ms | 0% |
| Site search | 2.71 | 471 ms | 678 ms | 839 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.762 | 74.3 ms | 84 ms | 96.2 ms | 0% |
| Page explorer | 1.54 | 314 ms | 348 ms | 445 ms | 0% |
| Page editor | 2.29 | 148 ms | 179 ms | 296 ms | 0% |
| Image library | 0.762 | 55.3 ms | 60.2 ms | 428 ms | 0% |
| Admin page search | 0.762 | 31.5 ms | 68.4 ms | 77.2 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.2 | 242 ms | 506 ms | 520 ms | 0% |
| Page explorer | 2.45 | 763 ms | 1.18 s | 1.28 s | 0% |
| Page editor | 3.64 | 363 ms | 678 ms | 742 ms | 0% |
| Image library | 1.21 | 200 ms | 396 ms | 472 ms | 0% |
| Admin page search | 1.21 | 77.3 ms | 252 ms | 439 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 s per level, after a 21 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 | 80 GB SSD | 78.6 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
- 78.6 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 03d80c2
- Product line
- General Purpose
- Location
- Mexico City, MX
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 80 GB SSD
- Virtualization
- KVM
- Network
- 1 Gbps
- Transfer
- 2.56 TB
- Port 25
- Unknown
- Monthly price at test time
- $15.00
- Hourly price at test time
- $0.021
- YABS version
- v2026-09-20
- Ran at
- Oct 18, 2026, 00:48:31 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 18, 2026, 00:46:00 UTC
- Server created
- Oct 18, 2026, 00:48:28 UTC
- First update from the server
- Oct 18, 2026, 00:48:28 UTC
- Completed
- Oct 18, 2026, 02:17:44 UTC
- Server deleted
- Oct 18, 2026, 02:17:44 UTC
- Cost of this run
- $0.032
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.