DigitalOcean v5 Shared 2 vCPU / 2 GB
Richmond 1
Server
-
ProviderDigitalOcean
-
Planv5 Shared 2 vCPU / 2 GB
-
LocationRichmond 1
-
vCPU2
-
RAM2 GB
-
Storage30 GB SSD
-
Network2 Gbps
-
OS imageubuntu-24-04-x64
-
TriggerScheduled
-
Queued atOct 15, 2026, 08:34:00 UTC
Referral link. If you sign up through it, I may get paid. How this works
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 2,334 | 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 |
2,250
|
Single-core only |
| Navigation |
2,130
|
Single-core only |
| HTML5 Browser |
2,432
|
Single-core only |
| PDF Viewer |
2,589
|
Single-core only |
| Photo Library |
2,085
|
Single-core only |
| Clang |
2,094
|
Single-core only |
| Text Processing |
2,324
|
Single-core only |
| Asset Compression |
2,322
|
Single-core only |
| HDR |
2,402
|
Single-core only |
| Photo Editor |
2,711
|
Single-core only |
| Ray Tracer |
2,041
|
Single-core only |
| Structure from Motion |
2,334
|
Single-core only |
| Game Physics |
2,261
|
Single-core only |
| Video Encoder |
2,468
|
Single-core only |
| Audio Encoder |
2,282
|
Single-core only |
| Video Player |
2,770
|
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 | 102 GB/s | 3 | 1.88% |
| Scale higher is better | 91.4 GB/s | 3 | 1.23% |
| Add higher is better | 92.9 GB/s | 3 | 1.77% |
| Triad higher is better | 93.1 GB/s | 3 | 1.37% |
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 | 678/s | 3 | 0.424% |
| RSA 4096 verifies higher is better | 44,573/s | 3 | 0.263% |
| SHA-256 higher is better | 2.48 GB/s | 3 | 0.608% |
| AES-256-GCM higher is better | 11.7 GB/s | 3 | 0.719% |
| ChaCha20-Poly1305 higher is better | 4.83 GB/s | 3 | 0.265% |
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 | 2.96 ms | 3 | 0.468% |
| Requests per second, 90th percentile higher is better | 675/s | 3 | 0.296% |
| Request latency, 99.9th percentile lower is better | 4.97 ms | 3 | 1.4% |
| Requests per second, average higher is better | 664/s | 3 | 0.381% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 8.8 MB/s (2,251 IOPS) | 8.8 MB/s (2,262 IOPS) | 17.6 MB/s (4,513 IOPS) |
| 64K | 35.8 MB/s (572 IOPS) | 36 MB/s (576 IOPS) | 71.8 MB/s (1,148 IOPS) |
| 512K | 34.3 MB/s (68 IOPS) | 36.4 MB/s (72 IOPS) | 70.6 MB/s (140 IOPS) |
| 1M | 22.9 MB/s (22 IOPS) | 25.3 MB/s (25 IOPS) | 48.3 MB/s (47 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.85 Gbps | 2.63 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.33 Gbps | 2.6 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 677 Mbps | 740 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.88 Gbps | 3.79 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.97 Gbps | 9.21 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 | 867 | 1.15 ms |
| fdatasync | 894 | 1.12 ms |
| fsync | 325 | 3.07 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 331 | 3.02 ms |
| Two 8 kB writes | ||
| open_datasync | 475 | 2.1 ms |
| fdatasync | 935 | 1.07 ms |
| fsync | 326 | 3.07 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 166 | 6.02 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 331 | 3.02 ms |
| 2 * 8kB open_sync writes | 167 | 5.99 ms |
| 4 * 4kB open_sync writes | 84.9 | 11.8 ms |
| 8 * 2kB open_sync writes | 41.6 | 24 ms |
| 16 * 1kB open_sync writes | 20.8 | 48 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 318 | 3.15 ms |
| write, close, fsync | 319 | 3.13 ms |
| Non-synced 8 kB writes | ||
| write | 834,131 | 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 | 738 | 1.26 ms | 1.79 ms | 3.12 ms | 7.04 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,292 | 2.6 ms | 7.24 ms | 11.1 ms | 20.8 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,380 | 6.03 ms | 27.6 ms | 50.7 ms | 149 ms | 0 |
| Read only | 1 | 40,709 | 0.024 ms | 0.028 ms | 0.033 ms | 0.05 ms | 0 |
| Read only | 8 | 100,858 | 0.068 ms | 0.114 ms | 0.13 ms | 0.181 ms | 0 |
| Read only | 32 | 84,353 | 0.319 ms | 0.464 ms | 0.631 ms | 1.01 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 4.16 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 | 500 | 1.8 ms | 2.62 ms | 5.99 ms | 22.5 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,487 | 2.79 ms | 16.9 ms | 46.7 ms | 90.4 ms | 0 |
| Read/write (TPC-B like) | 32 | 982 | 21.1 ms | 81.2 ms | 153 ms | 253 ms | 0 |
| Read only | 1 | 1,520 | 0.452 ms | 1.91 ms | 3.62 ms | 6.64 ms | 0 |
| Read only | 8 | 2,005 | 3.42 ms | 9.99 ms | 14.4 ms | 18.8 ms | 0 |
| Read only | 32 | 2,376 | 12.2 ms | 26.8 ms | 44.4 ms | 50.9 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 87.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 | 119 | 2,389 | 5.88 ms | 10.7 ms | 99.3 ms | 0 |
| Read/write | 8 | 363 | 7,268 | 10.7 ms | 117 ms | 200 ms | 0 |
| Read/write | 32 | 603 | 12,058 | 24.4 ms | 187 ms | 303 ms | 0 |
| Read only | 1 | 1,673 | 26,774 | 0.556 ms | 0.665 ms | 1.73 ms | 0 |
| Read only | 8 | 3,758 | 60,122 | 2.07 ms | 2.52 ms | 3.43 ms | 0 |
| Read only | 32 | 3,315 | 53,042 | 9.39 ms | 12.5 ms | 14 ms | 0 |
10 tables of 100,000 rows, loaded in 19.4 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 80,327 | 73,024 | 0.471 ms | 2.69 ms | 4.19 ms |
| 1:1 set:get | 79,897 | 39,948 | 0.479 ms | 2.72 ms | 4.35 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 | 1,059 | 3,874 | 5,184 | 363 ms |
| Express express-postgresjs | 10,439 | 16,422 | 61,769 | 45.7 ms |
| Fastify fastify-postgres | 10,244 | 16,730 | 66,175 | 48.9 ms |
| NestJS nestjs | 10,147 | 11,630 | 52,743 | 61.7 ms |
| Nuxt nuxt | 9,309 | 16,421 | 58,493 | 53.3 ms |
| FastAPI fastapi | 6,892 | 9,143 | 35,365 | 255 ms |
| Django django-postgresql | 3,196 | 3,580 | 9,120 | 165 ms |
| Rails rails | 5,118 | 7,398 | 30,242 | 68.4 ms |
| Laravel laravel | 1,263 | 1,360 | 2,534 | 213 ms |
| Symfony symfony | 1,545 | 1,680 | 5,439 | 176 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 | 4.09 | 392 ms | 464 ms | 485 ms | 0% |
| Shop page | 4.09 | 527 ms | 609 ms | 642 ms | 0% |
| Category page | 4.09 | 344 ms | 561 ms | 601 ms | 0% |
| Product page | 4.09 | 359 ms | 448 ms | 486 ms | 0% |
| Product search | 4.09 | 314 ms | 386 ms | 403 ms | 0% |
| 32 virtual users | |||||
| Home page | 4.15 | 1.42 s | 1.6 s | 1.66 s | 0% |
| Shop page | 4.15 | 1.85 s | 2.12 s | 2.22 s | 0% |
| Category page | 4.15 | 1.64 s | 1.96 s | 2.06 s | 0% |
| Product page | 4.15 | 1.42 s | 1.56 s | 1.6 s | 0% |
| Product search | 4.15 | 1.32 s | 1.46 s | 1.5 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 7.89 | 425 ms | 491 ms | 512 ms | 0% |
| Cart | 7.89 | 347 ms | 399 ms | 411 ms | 0% |
| Checkout | 7.89 | 265 ms | 311 ms | 325 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 7.87 | 1.39 s | 1.68 s | 1.73 s | 0% |
| Cart | 7.87 | 1.45 s | 1.62 s | 1.69 s | 0% |
| Checkout | 7.87 | 1.17 s | 1.36 s | 1.44 s | 0% |
k6 with a fixed number of virtual users, 61 to 62 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 | 4.02 | 108 ms | 138 ms | 254 ms | 0% |
| Topic JSON | 2.03 | 54.9 ms | 68.4 ms | 171 ms | 0% |
| Home page | 2.03 | 97.2 ms | 193 ms | 320 ms | 0% |
| Categories page | 1.01 | 110 ms | 136 ms | 173 ms | 0% |
| User activity page | 1.01 | 69.2 ms | 137 ms | 217 ms | 0% |
| 4 virtual users | |||||
| Topic page | 6.51 | 266 ms | 410 ms | 788 ms | 0% |
| Topic JSON | 3.25 | 138 ms | 195 ms | 294 ms | 0% |
| Home page | 3.21 | 231 ms | 344 ms | 595 ms | 0% |
| Categories page | 1.66 | 268 ms | 577 ms | 822 ms | 0% |
| User activity page | 1.61 | 172 ms | 475 ms | 563 ms | 0% |
| 16 virtual users | |||||
| Topic page | 6.73 | 956 ms | 1.24 s | 1.38 s | 0% |
| Topic JSON | 3.41 | 835 ms | 1.01 s | 1.19 s | 0% |
| Home page | 3.39 | 918 ms | 1.13 s | 1.28 s | 0% |
| Categories page | 1.72 | 944 ms | 1.22 s | 1.5 s | 0% |
| User activity page | 1.69 | 844 ms | 1.04 s | 1.1 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 135 | 32.1 ms | 83.6 ms | 103 ms | 0% |
| Topic JSON | 67.4 | 30.3 ms | 84.4 ms | 108 ms | 0% |
| Home page | 67.3 | 31.3 ms | 84.7 ms | 104 ms | 0% |
| Categories page | 33.7 | 31.6 ms | 84.6 ms | 105 ms | 0% |
| User activity page | 33.7 | 107 ms | 171 ms | 284 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 495 MB of it. The container peaked at 1,510 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 17.4 | 15.4 ms | 18.6 ms | 27.5 ms | 0% |
| Post page | 43.5 | 8.75 ms | 11.6 ms | 18.6 ms | 0% |
| Tag page | 8.71 | 11 ms | 13.7 ms | 16.9 ms | 0% |
| Author page | 8.71 | 10.8 ms | 13.6 ms | 25 ms | 0% |
| RSS feed | 8.7 | 13.3 ms | 15.9 ms | 22.4 ms | 0% |
| 4 virtual users | |||||
| Home page | 19.7 | 50 ms | 69.7 ms | 99.9 ms | 0% |
| Post page | 49.3 | 38.3 ms | 54.9 ms | 81.7 ms | 0% |
| Tag page | 9.88 | 32.8 ms | 48.3 ms | 75 ms | 0% |
| Author page | 9.84 | 32.7 ms | 47.6 ms | 70.1 ms | 0% |
| RSS feed | 9.84 | 34.3 ms | 49.8 ms | 73.5 ms | 0% |
| 16 virtual users | |||||
| Home page | 19.2 | 205 ms | 286 ms | 302 ms | 0% |
| Post page | 47.9 | 170 ms | 243 ms | 266 ms | 0% |
| Tag page | 9.58 | 112 ms | 175 ms | 195 ms | 0% |
| Author page | 9.61 | 113 ms | 172 ms | 194 ms | 0% |
| RSS feed | 9.58 | 114 ms | 169 ms | 202 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 7.28 | 17.1 ms | 22.6 ms | 32.2 ms | 0% |
| Post editor | 21.8 | 6.88 ms | 9.93 ms | 14.1 ms | 0% |
| Saving a draft | 21.8 | 23.7 ms | 30.3 ms | 41.3 ms | 0% |
| Member list | 7.28 | 19.5 ms | 24.3 ms | 28.4 ms | 0% |
| 4 virtual users | |||||
| Post list | 9.74 | 20.4 ms | 27.9 ms | 43.7 ms | 0% |
| Post editor | 29.3 | 8.77 ms | 13.5 ms | 19.1 ms | 0% |
| Saving a draft | 29.3 | 108 ms | 142 ms | 170 ms | 0% |
| Member list | 9.75 | 23.1 ms | 27.9 ms | 47.7 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 386 MB and MySQL at 585 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 3.43 | 38.9 ms | 44.8 ms | 47.9 ms | 0% |
| Blog index | 3.43 | 125 ms | 153 ms | 165 ms | 0% |
| Blog post | 10.2 | 12.4 ms | 19.2 ms | 21 ms | 0% |
| Bread page | 10.3 | 13.7 ms | 16.3 ms | 17.2 ms | 0% |
| Location page | 3.43 | 13 ms | 15.7 ms | 16.4 ms | 0% |
| Site search | 3.41 | 23.3 ms | 38.7 ms | 40 ms | 0% |
| 4 virtual users | |||||
| Home page | 4.76 | 112 ms | 177 ms | 198 ms | 0% |
| Blog index | 4.76 | 400 ms | 579 ms | 623 ms | 0% |
| Blog post | 14.3 | 34.1 ms | 58.4 ms | 81.5 ms | 0% |
| Bread page | 14.3 | 36.6 ms | 57.5 ms | 65.8 ms | 0% |
| Location page | 4.79 | 35.1 ms | 54.9 ms | 74.7 ms | 0% |
| Site search | 4.74 | 54.2 ms | 114 ms | 140 ms | 0% |
| 16 virtual users | |||||
| Home page | 5.4 | 341 ms | 476 ms | 565 ms | 0% |
| Blog index | 5.42 | 851 ms | 1.02 s | 1.09 s | 0% |
| Blog post | 16.1 | 195 ms | 309 ms | 407 ms | 0% |
| Bread page | 16.1 | 203 ms | 320 ms | 390 ms | 0% |
| Location page | 5.38 | 205 ms | 336 ms | 399 ms | 0% |
| Site search | 5.37 | 252 ms | 409 ms | 487 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 1.24 | 43.3 ms | 47.3 ms | 63.3 ms | 0% |
| Page explorer | 2.5 | 191 ms | 208 ms | 332 ms | 0% |
| Page editor | 3.73 | 93.4 ms | 116 ms | 216 ms | 0% |
| Image library | 1.24 | 33.6 ms | 39.2 ms | 175 ms | 0% |
| Admin page search | 1.24 | 18.3 ms | 41.7 ms | 45.1 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.87 | 161 ms | 378 ms | 412 ms | 0% |
| Page explorer | 3.78 | 486 ms | 791 ms | 855 ms | 0% |
| Page editor | 5.68 | 227 ms | 444 ms | 529 ms | 0% |
| Image library | 1.9 | 135 ms | 346 ms | 437 ms | 0% |
| Admin page search | 1.87 | 51.4 ms | 145 ms | 224 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 307 MB, Postgres at 170 MB, and Redis at 29 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 30 GB SSD | 29 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 9555P 64-Core Processor
- CPU cores
- 2
- CPU frequency
- 3195 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 29 GiB
- Virtualization reported
- KVM
- CPU steal
- 0% of busy CPU time stolen
- Distro
- Ubuntu 24.04.5 LTS
- Kernel
- 6.8.0-142-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- Yes
Advertised at test time
- Plan
- v5 Shared 2 vCPU / 2 GB
- Product line
- v5 Shared
- Location
- Richmond 1
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 30 GB SSD
- Virtualization
- KVM
- Network
- 2 Gbps
- Transfer
- 3 TB
- Port 25
- Closed
- Monthly price at test time
- $32.61
- Hourly price at test time
- $0.044
- YABS version
- v2026-09-20
- Ran at
- Oct 15, 2026, 08:36:36 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 15, 2026, 08:34:00 UTC
- Server created
- Oct 15, 2026, 08:35:09 UTC
- First update from the server
- Oct 15, 2026, 08:35:09 UTC
- Completed
- Oct 15, 2026, 10:11:02 UTC
- Server deleted
- Oct 15, 2026, 10:11:02 UTC
- Cost of this run
- $0.071
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.