OneProvider General Purpose 03d40c2
San Juan, PR
Server
-
ProviderOneProvider
-
PlanGeneral Purpose 03d40c2
-
LocationSan Juan, PR
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
Network1 Gbps
-
OS image1194
-
TriggerScheduled
-
Queued atOct 13, 2026, 19:54:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 631 | 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 |
617
|
Single-core only |
| Navigation |
661
|
Single-core only |
| HTML5 Browser |
556
|
Single-core only |
| PDF Viewer |
741
|
Single-core only |
| Photo Library |
565
|
Single-core only |
| Clang |
677
|
Single-core only |
| Text Processing |
639
|
Single-core only |
| Asset Compression |
570
|
Single-core only |
| HDR |
644
|
Single-core only |
| Photo Editor |
600
|
Single-core only |
| Ray Tracer |
648
|
Single-core only |
| Structure from Motion |
715
|
Single-core only |
| Game Physics |
617
|
Single-core only |
| Video Encoder |
610
|
Single-core only |
| Audio Encoder |
694
|
Single-core only |
| Video Player |
581
|
Single-core only |
Rank among the 150 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 | 13.3 GB/s | 3 | 5.68% |
| Scale higher is better | 10.9 GB/s | 3 | 6.26% |
| Add higher is better | 12.7 GB/s | 3 | 4.11% |
| Triad higher is better | 12.5 GB/s | 3 | 3.27% |
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 | 316/s | 3 | 3.94% |
| RSA 4096 verifies higher is better | 20,594/s | 3 | 1.64% |
| SHA-256 higher is better | 359 MB/s | 3 | 1.71% |
| AES-256-GCM higher is better | 4.89 GB/s | 3 | 1.02% |
| ChaCha20-Poly1305 higher is better | 2.31 GB/s | 3 | 0.875% |
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 | 5.68 ms | 3 | 0.163% |
| Requests per second, 90th percentile higher is better | 343/s | 3 | 0.292% |
| Request latency, 99.9th percentile lower is better | 14.6 ms | 3 | 4.54% |
| Requests per second, average higher is better | 334/s | 3 | 0.607% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 60.2 MB/s (15,409 IOPS) | 60.3 MB/s (15,437 IOPS) | 120.5 MB/s (30,846 IOPS) |
| 64K | 448.6 MB/s (7,178 IOPS) | 451 MB/s (7,215 IOPS) | 899.6 MB/s (14,393 IOPS) |
| 512K | 449 MB/s (898 IOPS) | 472.9 MB/s (945 IOPS) | 921.9 MB/s (1,843 IOPS) |
| 1M | 436.4 MB/s (436 IOPS) | 465.4 MB/s (465 IOPS) | 901.8 MB/s (901 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.44 Gbps | 599 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 294 Mbps | 1.43 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 699 Mbps | 844 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 2.32 Gbps | 857 Mbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 3.82 Gbps | 1.35 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,782 | 0.561 ms |
| fdatasync | 1,689 | 0.592 ms |
| fsync | 669 | 1.49 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 666 | 1.5 ms |
| Two 8 kB writes | ||
| open_datasync | 862 | 1.16 ms |
| fdatasync | 1,405 | 0.712 ms |
| fsync | 638 | 1.57 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 335 | 2.98 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 625 | 1.6 ms |
| 2 * 8kB open_sync writes | 357 | 2.8 ms |
| 4 * 4kB open_sync writes | 198 | 5.06 ms |
| 8 * 2kB open_sync writes | 93.7 | 10.7 ms |
| 16 * 1kB open_sync writes | 56.6 | 17.7 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 661 | 1.51 ms |
| write, close, fsync | 698 | 1.43 ms |
| Non-synced 8 kB writes | ||
| write | 332,964 | 0.003 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 | 739 | 1.21 ms | 2.19 ms | 2.92 ms | 8.55 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,315 | 3.01 ms | 6.4 ms | 9.91 ms | 17.3 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,231 | 11.2 ms | 34 ms | 57.1 ms | 152 ms | 0 |
| Read only | 1 | 14,220 | 0.065 ms | 0.103 ms | 0.142 ms | 0.297 ms | 0 |
| Read only | 8 | 29,627 | 0.24 ms | 0.412 ms | 0.52 ms | 1.22 ms | 0 |
| Read only | 32 | 26,432 | 0.986 ms | 1.83 ms | 2.61 ms | 5.4 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 4.37 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 | 552 | 1.64 ms | 3 ms | 4.41 ms | 11.5 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,806 | 3.8 ms | 8.55 ms | 17.1 ms | 32.9 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,142 | 13.4 ms | 25.1 ms | 42.3 ms | 82.8 ms | 0 |
| Read only | 1 | 3,287 | 0.272 ms | 0.556 ms | 0.96 ms | 2.37 ms | 0 |
| Read only | 8 | 15,257 | 0.433 ms | 0.998 ms | 1.94 ms | 3.29 ms | 0 |
| Read only | 32 | 15,781 | 1.68 ms | 3.52 ms | 5.35 ms | 9.67 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 43.1 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 | 146 | 2,913 | 5.77 ms | 11.7 ms | 33.1 ms | 0 |
| Read/write | 8 | 425 | 8,495 | 17 ms | 36.9 ms | 52.9 ms | 0 |
| Read/write | 32 | 449 | 8,972 | 70.5 ms | 115 ms | 148 ms | 0 |
| Read only | 1 | 477 | 7,627 | 1.96 ms | 2.97 ms | 4.25 ms | 0 |
| Read only | 8 | 912 | 14,585 | 8.43 ms | 12.5 ms | 15.3 ms | 0 |
| Read only | 32 | 823 | 13,163 | 38.2 ms | 51 ms | 58.9 ms | 0 |
10 tables of 100,000 rows, loaded in 17.3 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 32,144 | 29,222 | 1.98 ms | 4.96 ms | 7.65 ms |
| 1:1 set:get | 30,784 | 15,392 | 2.08 ms | 5.09 ms | 7.97 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 | 266 | 1,016 | 1,546 | 1.94 s |
| Express express-postgresjs | 4,343 | 6,189 | 15,123 | 163 ms |
| Fastify fastify-postgres | 4,388 | 6,176 | 15,855 | 119 ms |
| NestJS nestjs | 2,378 | 2,608 | 9,138 | 191 ms |
| Nuxt nuxt | 3,681 | 5,673 | 13,203 | 915 ms |
| FastAPI fastapi | 1,922 | 2,391 | 9,262 | 567 ms |
| Django django-postgresql | 640 | 596 | 1,690 | 600 ms |
| Rails rails | 1,077 | 1,581 | 5,547 | 315 ms |
| Laravel laravel | 360 | 382 | 710 | 782 ms |
| Symfony symfony | 471 | 513 | 1,458 | 596 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.
WooCommerce
Page mix
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Home page | 1.04 | 1.49 s | 1.6 s | 1.62 s | 0% |
| Shop page | 1.04 | 2 s | 2.21 s | 2.23 s | 0% |
| Category page | 1.04 | 1.26 s | 2.09 s | 2.15 s | 0% |
| Product page | 1.04 | 1.39 s | 1.53 s | 1.56 s | 0% |
| Product search | 1.04 | 1.24 s | 1.39 s | 1.43 s | 0% |
| 32 virtual users | |||||
| Home page | 1.33 | 5.21 s | 6.04 s | 6.2 s | 0% |
| Shop page | 1.16 | 7.04 s | 8.13 s | 8.25 s | 0% |
| Category page | 0.898 | 6.45 s | 7.76 s | 8.22 s | 0% |
| Product page | 0.898 | 5.27 s | 5.59 s | 5.68 s | 0% |
| Product search | 0.898 | 4.99 s | 5.29 s | 5.42 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 1.94 | 1.62 s | 1.79 s | 1.84 s | 0% |
| Cart | 1.94 | 1.27 s | 1.43 s | 1.54 s | 0% |
| Checkout | 1.94 | 977 ms | 1.09 s | 1.13 s | 0% |
| 32 virtual users | |||||
| Add to cart | 2.1 | 5.1 s | 6.25 s | 6.36 s | 0% |
| Cart | 2.1 | 5.42 s | 5.97 s | 6.01 s | 0% |
| Checkout | 1.91 | 4.33 s | 5.02 s | 5.1 s | 0% |
k6 with a fixed number of virtual users, 64 to 71 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 | 1.01 | 440 ms | 537 ms | 952 ms | 0% |
| Topic JSON | 0.504 | 215 ms | 234 ms | 247 ms | 0% |
| Home page | 0.504 | 395 ms | 485 ms | 868 ms | 0% |
| Categories page | 0.26 | 459 ms | 542 ms | 610 ms | 0% |
| User activity page | 0.244 | 269 ms | 311 ms | 312 ms | 0% |
| 4 virtual users | |||||
| Topic page | 1.49 | 1.13 s | 1.67 s | 2.32 s | 0% |
| Topic JSON | 0.747 | 615 ms | 717 ms | 746 ms | 0% |
| Home page | 0.747 | 997 ms | 1.72 s | 2.14 s | 0% |
| Categories page | 0.39 | 1.23 s | 1.83 s | 2.46 s | 0% |
| User activity page | 0.374 | 681 ms | 1.12 s | 1.2 s | 0% |
| 16 virtual users | |||||
| Topic page | 1.58 | 2.13 s | 2.66 s | 3.24 s | 0% |
| Topic JSON | 0.813 | 1.63 s | 2.42 s | 2.74 s | 0% |
| Home page | 0.813 | 2.1 s | 2.81 s | 3.21 s | 0% |
| Categories page | 0.382 | 2.17 s | 2.59 s | 2.74 s | 0% |
| User activity page | 0.414 | 1.7 s | 2.22 s | 2.82 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 34.5 | 132 ms | 280 ms | 379 ms | 0.0477% |
| Topic JSON | 17.3 | 132 ms | 280 ms | 372 ms | 0.38% |
| Home page | 17.3 | 138 ms | 279 ms | 363 ms | 0.381% |
| Categories page | 8.63 | 130 ms | 275 ms | 481 ms | 0.191% |
| User activity page | 8.65 | 396 ms | 686 ms | 951 ms | 0% |
k6 with a fixed number of virtual users, 61 to 63 s per level, after a 23 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 404 MB of it. The container peaked at 1,459 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 3.76 | 73.4 ms | 90.8 ms | 108 ms | 0% |
| Post page | 9.39 | 40.5 ms | 51.7 ms | 78.2 ms | 0% |
| Tag page | 1.88 | 50.4 ms | 61.4 ms | 65.3 ms | 0% |
| Author page | 1.88 | 50 ms | 68.1 ms | 101 ms | 0% |
| RSS feed | 1.88 | 58 ms | 73.5 ms | 108 ms | 0% |
| 4 virtual users | |||||
| Home page | 4.77 | 215 ms | 293 ms | 370 ms | 0% |
| Post page | 12 | 150 ms | 214 ms | 310 ms | 0% |
| Tag page | 2.41 | 142 ms | 196 ms | 269 ms | 0% |
| Author page | 2.4 | 138 ms | 198 ms | 236 ms | 0% |
| RSS feed | 2.4 | 154 ms | 266 ms | 323 ms | 0% |
| 16 virtual users | |||||
| Home page | 4.83 | 855 ms | 1.02 s | 1.09 s | 0% |
| Post page | 12 | 683 ms | 897 ms | 979 ms | 0% |
| Tag page | 2.4 | 471 ms | 672 ms | 695 ms | 0% |
| Author page | 2.39 | 465 ms | 620 ms | 688 ms | 0% |
| RSS feed | 2.39 | 479 ms | 646 ms | 707 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 2.02 | 71.4 ms | 98.1 ms | 140 ms | 0% |
| Post editor | 6.08 | 28.5 ms | 39.9 ms | 48 ms | 0% |
| Saving a draft | 6.06 | 72.2 ms | 94.1 ms | 110 ms | 0% |
| Member list | 2.02 | 86.2 ms | 114 ms | 150 ms | 0% |
| 4 virtual users | |||||
| Post list | 2.68 | 92.2 ms | 128 ms | 214 ms | 0% |
| Post editor | 8.12 | 47.2 ms | 68.6 ms | 95 ms | 0% |
| Saving a draft | 8.15 | 354 ms | 483 ms | 563 ms | 0% |
| Member list | 2.71 | 105 ms | 125 ms | 210 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. 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 338 MB and MySQL at 586 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 0.713 | 182 ms | 211 ms | 224 ms | 0% |
| Blog index | 0.713 | 653 ms | 710 ms | 721 ms | 0% |
| Blog post | 2.11 | 58.5 ms | 93.6 ms | 107 ms | 0% |
| Bread page | 2.12 | 64.8 ms | 78.7 ms | 82.8 ms | 0% |
| Location page | 0.713 | 61.7 ms | 76.6 ms | 80.9 ms | 0% |
| Site search | 0.697 | 104 ms | 181 ms | 188 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.35 | 444 ms | 611 ms | 727 ms | 0% |
| Blog index | 1.38 | 1.35 s | 1.91 s | 1.98 s | 0% |
| Blog post | 4.05 | 117 ms | 211 ms | 273 ms | 0% |
| Bread page | 4.08 | 126 ms | 197 ms | 226 ms | 0% |
| Location page | 1.4 | 122 ms | 184 ms | 225 ms | 0% |
| Site search | 1.33 | 175 ms | 397 ms | 427 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.25 | 1.48 s | 1.95 s | 2.18 s | 0% |
| Blog index | 1.33 | 3.68 s | 4.36 s | 4.67 s | 0% |
| Blog post | 3.79 | 800 ms | 1.3 s | 1.56 s | 0% |
| Bread page | 3.82 | 843 ms | 1.29 s | 1.59 s | 0% |
| Location page | 1.3 | 805 ms | 1.15 s | 1.31 s | 0% |
| Site search | 1.26 | 934 ms | 1.56 s | 1.64 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.308 | 194 ms | 237 ms | 243 ms | 0% |
| Page explorer | 0.649 | 711 ms | 782 ms | 873 ms | 0% |
| Page editor | 0.942 | 342 ms | 430 ms | 624 ms | 0% |
| Image library | 0.308 | 131 ms | 336 ms | 1.45 s | 0% |
| Admin page search | 0.308 | 76.7 ms | 168 ms | 266 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.55 | 421 ms | 863 ms | 1.03 s | 0% |
| Page explorer | 1.1 | 1.6 s | 2.73 s | 3.29 s | 0% |
| Page editor | 1.65 | 724 ms | 1.41 s | 1.88 s | 0% |
| Image library | 0.55 | 448 ms | 904 ms | 1.01 s | 0% |
| Admin page search | 0.55 | 210 ms | 470 ms | 520 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. 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 290 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0.1% 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
- 2095 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.1% 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
- San Juan, PR
- 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 13, 2026, 19:57:17 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 13, 2026, 19:54:00 UTC
- First update from the server
- Oct 13, 2026, 19:56:35 UTC
- Completed
- Oct 13, 2026, 21:40:38 UTC
- Server deleted
- Oct 13, 2026, 21:40:38 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.