DigitalOcean Basic AMD 2 vCPU / 2 GB
Server
-
ProviderDigitalOcean
-
PlanBasic AMD 2 vCPU / 2 GB
-
LocationNew York 1
-
vCPU2
-
RAM2 GB
-
Storage60 GB NVMe
-
Network2 Gbps
-
OS imageubuntu-24-04-x64
-
TriggerScheduled
-
Queued atOct 14, 2026, 12:15: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 | 917 | 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,072
|
Single-core only |
| Navigation |
939
|
Single-core only |
| HTML5 Browser |
753
|
Single-core only |
| PDF Viewer |
982
|
Single-core only |
| Photo Library |
877
|
Single-core only |
| Clang |
800
|
Single-core only |
| Text Processing |
798
|
Single-core only |
| Asset Compression |
948
|
Single-core only |
| HDR |
750
|
Single-core only |
| Photo Editor |
1,033
|
Single-core only |
| Ray Tracer |
835
|
Single-core only |
| Structure from Motion |
1,032
|
Single-core only |
| Game Physics |
994
|
Single-core only |
| Video Encoder |
895
|
Single-core only |
| Audio Encoder |
1,092
|
Single-core only |
| Video Player |
976
|
Single-core only |
Rank among the 156 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 | 34.8 GB/s | 3 | 3.06% |
| Scale higher is better | 25.4 GB/s | 3 | 3.6% |
| Add higher is better | 26.8 GB/s | 3 | 3.08% |
| Triad higher is better | 27.2 GB/s | 3 | 2.19% |
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 | 373/s | 3 | 2.27% |
| RSA 4096 verifies higher is better | 23,660/s | 3 | 3.86% |
| SHA-256 higher is better | 1.12 GB/s | 3 | 1.71% |
| AES-256-GCM higher is better | 5.71 GB/s | 3 | 1.07% |
| ChaCha20-Poly1305 higher is better | 2.93 GB/s | 3 | 3.14% |
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.09 ms | 3 | 1.73% |
| Requests per second, 90th percentile higher is better | 391/s | 3 | 3.85% |
| Request latency, 99.9th percentile lower is better | 12.4 ms | 3 | 4.5% |
| Requests per second, average higher is better | 371/s | 3 | 2.26% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 90.2 MB/s (23,085 IOPS) | 90.4 MB/s (23,146 IOPS) | 180.6 MB/s (46,231 IOPS) |
| 64K | 612.8 MB/s (9,805 IOPS) | 616.1 MB/s (9,857 IOPS) | 1.2 GB/s (19,662 IOPS) |
| 512K | 458.7 MB/s (917 IOPS) | 483.1 MB/s (966 IOPS) | 941.8 MB/s (1,883 IOPS) |
| 1M | 233.6 MB/s (233 IOPS) | 249.2 MB/s (249 IOPS) | 482.8 MB/s (482 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.88 Gbps | 1.79 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.86 Gbps | 1.79 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 805 Mbps | 809 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.53 Gbps | 1.31 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 2.01 Gbps | 1.89 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,888 | 0.257 ms |
| fdatasync | 3,705 | 0.27 ms |
| fsync | 1,346 | 0.743 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,510 | 0.662 ms |
| Two 8 kB writes | ||
| open_datasync | 1,811 | 0.552 ms |
| fdatasync | 3,018 | 0.331 ms |
| fsync | 1,438 | 0.696 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 782 | 1.28 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 1,181 | 0.846 ms |
| 2 * 8kB open_sync writes | 631 | 1.59 ms |
| 4 * 4kB open_sync writes | 372 | 2.69 ms |
| 8 * 2kB open_sync writes | 194 | 5.15 ms |
| 16 * 1kB open_sync writes | 97.6 | 10.2 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 1,508 | 0.663 ms |
| write, close, fsync | 1,389 | 0.72 ms |
| Non-synced 8 kB writes | ||
| write | 454,677 | 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,185 | 0.758 ms | 1.19 ms | 2.58 ms | 5.75 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,748 | 2.51 ms | 5.26 ms | 9.45 ms | 29.1 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,742 | 8.9 ms | 28.8 ms | 49 ms | 90.3 ms | 0 |
| Read only | 1 | 17,156 | 0.053 ms | 0.088 ms | 0.115 ms | 0.247 ms | 0 |
| Read only | 8 | 33,716 | 0.209 ms | 0.37 ms | 0.494 ms | 1.8 ms | 0 |
| Read only | 32 | 32,234 | 0.785 ms | 1.61 ms | 2.37 ms | 5.16 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.97 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 | 694 | 1.31 ms | 2.1 ms | 5.4 ms | 11.7 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,035 | 3.48 ms | 7.65 ms | 12.2 ms | 19.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 2,474 | 11.9 ms | 22.1 ms | 30 ms | 42.8 ms | 0 |
| Read only | 1 | 2,519 | 0.353 ms | 0.748 ms | 1.59 ms | 2.75 ms | 0 |
| Read only | 8 | 16,079 | 0.381 ms | 1.17 ms | 2.14 ms | 3.69 ms | 0 |
| Read only | 32 | 18,264 | 1.39 ms | 3.64 ms | 5.34 ms | 9.05 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 31.9 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 | 184 | 3,689 | 5 ms | 8.28 ms | 17 ms | 0 |
| Read/write | 8 | 508 | 10,161 | 15.3 ms | 24.4 ms | 32.5 ms | 0 |
| Read/write | 32 | 554 | 11,086 | 55.8 ms | 101 ms | 128 ms | 0 |
| Read only | 1 | 592 | 9,467 | 1.61 ms | 2.26 ms | 2.76 ms | 0 |
| Read only | 8 | 1,084 | 17,348 | 7.04 ms | 10.3 ms | 12.3 ms | 0 |
| Read only | 32 | 964 | 15,431 | 32.5 ms | 44.2 ms | 51.9 ms | 0 |
10 tables of 100,000 rows, loaded in 12.6 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 42,078 | 38,252 | 1.3 ms | 4.03 ms | 5.86 ms |
| 1:1 set:get | 44,109 | 22,054 | 1.14 ms | 3.89 ms | 5.6 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 | 366 | 1,298 | 2,016 | 1.68 s |
| Express express-postgresjs | 5,237 | 6,690 | 18,468 | 115 ms |
| Fastify fastify-postgres | 5,124 | 8,023 | 19,352 | 107 ms |
| NestJS nestjs | 2,784 | 3,277 | 10,640 | 155 ms |
| Nuxt nuxt | 4,713 | 7,290 | 17,701 | 118 ms |
| FastAPI fastapi | 2,163 | 2,948 | 11,062 | 704 ms |
| Django django-postgresql | 1,223 | 1,268 | 3,215 | 322 ms |
| Rails rails | 1,858 | 2,631 | 8,947 | 206 ms |
| Laravel laravel | 459 | 486 | 1,037 | 681 ms |
| Symfony symfony | 607 | 663 | 2,274 | 468 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 | 1.42 | 1.13 s | 1.35 s | 1.41 s | 0% |
| Shop page | 1.42 | 1.49 s | 1.72 s | 1.81 s | 0% |
| Category page | 1.42 | 899 ms | 1.55 s | 1.74 s | 0% |
| Product page | 1.42 | 1.03 s | 1.17 s | 1.25 s | 0% |
| Product search | 1.42 | 887 ms | 1.08 s | 1.16 s | 0% |
| 32 virtual users | |||||
| Home page | 1.39 | 4.15 s | 5.06 s | 5.34 s | 0% |
| Shop page | 1.39 | 5.67 s | 6.47 s | 6.61 s | 0% |
| Category page | 1.39 | 4.83 s | 5.99 s | 6.32 s | 0% |
| Product page | 1.39 | 4.01 s | 4.39 s | 4.47 s | 0% |
| Product search | 1.39 | 3.79 s | 4.04 s | 4.08 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 2.79 | 1.16 s | 1.42 s | 1.54 s | 0% |
| Cart | 2.79 | 936 ms | 1.16 s | 1.26 s | 0% |
| Checkout | 2.79 | 727 ms | 900 ms | 1.01 s | 0% |
| 32 virtual users | |||||
| Add to cart | 2.54 | 4.36 s | 5.6 s | 5.8 s | 0% |
| Cart | 2.54 | 4.45 s | 5.05 s | 5.22 s | 0% |
| Checkout | 2.54 | 3.51 s | 4.07 s | 4.23 s | 0% |
k6 with a fixed number of virtual users, 62 to 69 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.33 | 330 ms | 480 ms | 681 ms | 0% |
| Topic JSON | 0.673 | 172 ms | 227 ms | 467 ms | 0% |
| Home page | 0.673 | 292 ms | 399 ms | 579 ms | 0% |
| Categories page | 0.345 | 353 ms | 431 ms | 525 ms | 0% |
| User activity page | 0.328 | 190 ms | 295 ms | 299 ms | 0% |
| 4 virtual users | |||||
| Topic page | 1.97 | 839 ms | 1.33 s | 1.65 s | 0% |
| Topic JSON | 0.975 | 467 ms | 680 ms | 841 ms | 0% |
| Home page | 0.975 | 773 ms | 1.63 s | 2.01 s | 0% |
| Categories page | 0.52 | 878 ms | 1.29 s | 1.96 s | 0% |
| User activity page | 0.488 | 526 ms | 860 ms | 1.03 s | 0% |
| 16 virtual users | |||||
| Topic page | 2.19 | 1.96 s | 2.49 s | 2.85 s | 0% |
| Topic JSON | 1.09 | 1.7 s | 2.14 s | 2.31 s | 0% |
| Home page | 1.09 | 1.89 s | 2.35 s | 2.58 s | 0% |
| Categories page | 0.547 | 1.96 s | 2.41 s | 2.43 s | 0% |
| User activity page | 0.547 | 1.62 s | 2.13 s | 2.23 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 45.1 | 102 ms | 244 ms | 332 ms | 0% |
| Topic JSON | 22.6 | 98.9 ms | 237 ms | 313 ms | 0% |
| Home page | 22.6 | 102 ms | 238 ms | 335 ms | 0% |
| Categories page | 11.3 | 104 ms | 250 ms | 385 ms | 0% |
| User activity page | 11.3 | 309 ms | 495 ms | 643 ms | 0% |
k6 with a fixed number of virtual users, 60 to 62 s per level, after a 22 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 497 MB of it. The container peaked at 1,503 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 5.46 | 52.9 ms | 69.3 ms | 78.4 ms | 0% |
| Post page | 13.6 | 27 ms | 35.2 ms | 40.7 ms | 0% |
| Tag page | 2.73 | 33.9 ms | 43.8 ms | 59.9 ms | 0% |
| Author page | 2.71 | 35.6 ms | 47.6 ms | 64.4 ms | 0% |
| RSS feed | 2.71 | 40.8 ms | 53.7 ms | 61.6 ms | 0% |
| 4 virtual users | |||||
| Home page | 6.18 | 172 ms | 242 ms | 287 ms | 0% |
| Post page | 15.4 | 116 ms | 170 ms | 207 ms | 0% |
| Tag page | 3.11 | 104 ms | 160 ms | 198 ms | 0% |
| Author page | 3.09 | 111 ms | 165 ms | 214 ms | 0% |
| RSS feed | 3.07 | 114 ms | 165 ms | 188 ms | 0% |
| 16 virtual users | |||||
| Home page | 6.34 | 635 ms | 788 ms | 880 ms | 0% |
| Post page | 15.9 | 527 ms | 676 ms | 725 ms | 0% |
| Tag page | 3.18 | 349 ms | 444 ms | 512 ms | 0% |
| Author page | 3.2 | 345 ms | 474 ms | 526 ms | 0% |
| RSS feed | 3.18 | 353 ms | 477 ms | 576 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 2.85 | 50.6 ms | 70.7 ms | 109 ms | 0% |
| Post editor | 8.6 | 19.3 ms | 29 ms | 42.4 ms | 0% |
| Saving a draft | 8.6 | 51.1 ms | 73 ms | 96.5 ms | 0% |
| Member list | 2.87 | 61.8 ms | 81.4 ms | 93.2 ms | 0% |
| 4 virtual users | |||||
| Post list | 3.24 | 72.5 ms | 104 ms | 138 ms | 0% |
| Post editor | 9.75 | 35 ms | 54.4 ms | 91.8 ms | 0% |
| Saving a draft | 9.78 | 302 ms | 427 ms | 494 ms | 0% |
| Member list | 3.26 | 88 ms | 123 ms | 159 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 346 MB and MySQL at 585 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.1 | 122 ms | 154 ms | 167 ms | 0% |
| Blog index | 1.1 | 411 ms | 501 ms | 549 ms | 0% |
| Blog post | 3.27 | 37.2 ms | 60.7 ms | 76.7 ms | 0% |
| Bread page | 3.29 | 42.1 ms | 53.6 ms | 60.8 ms | 0% |
| Location page | 1.1 | 39.5 ms | 51.3 ms | 57.6 ms | 0% |
| Site search | 1.1 | 57.9 ms | 101 ms | 113 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.85 | 306 ms | 430 ms | 488 ms | 0% |
| Blog index | 1.88 | 974 ms | 1.45 s | 1.51 s | 0% |
| Blog post | 5.56 | 89.4 ms | 156 ms | 188 ms | 0% |
| Bread page | 5.61 | 93.5 ms | 147 ms | 165 ms | 0% |
| Location page | 1.9 | 91.8 ms | 140 ms | 212 ms | 0% |
| Site search | 1.85 | 130 ms | 279 ms | 323 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.02 | 912 ms | 1.41 s | 1.51 s | 0% |
| Blog index | 2.04 | 2.24 s | 2.74 s | 3.22 s | 0% |
| Blog post | 6.08 | 503 ms | 971 ms | 1.64 s | 0% |
| Bread page | 6.08 | 484 ms | 932 ms | 1.4 s | 0% |
| Location page | 2.07 | 458 ms | 822 ms | 1.27 s | 0% |
| Site search | 2.04 | 575 ms | 1.05 s | 1.24 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.412 | 125 ms | 177 ms | 179 ms | 0% |
| Page explorer | 0.856 | 546 ms | 804 ms | 969 ms | 0% |
| Page editor | 1.28 | 258 ms | 387 ms | 453 ms | 0% |
| Image library | 0.428 | 94.3 ms | 137 ms | 907 ms | 0% |
| Admin page search | 0.412 | 51.6 ms | 134 ms | 164 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.67 | 491 ms | 657 ms | 946 ms | 0% |
| Page explorer | 1.39 | 1.55 s | 2.28 s | 2.7 s | 0% |
| Page editor | 2.06 | 642 ms | 1.02 s | 1.1 s | 0% |
| Image library | 0.686 | 308 ms | 682 ms | 772 ms | 0% |
| Admin page search | 0.67 | 143 ms | 374 ms | 417 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 294 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 | 60 GB NVMe | 58 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
- DO-Premium-AMD
- CPU cores
- 2
- CPU frequency
- 1996 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 58 GiB
- Virtualization reported
- KVM
- CPU steal
- 0.2% 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
- Basic AMD 2 vCPU / 2 GB
- Product line
- Basic AMD
- Location
- New York 1
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 60 GB NVMe
- Virtualization
- KVM
- Network
- 2 Gbps
- Transfer
- 3 TB
- Port 25
- Closed
- Monthly price at test time
- $21.00
- Hourly price at test time
- $0.031
- YABS version
- v2026-09-20
- Ran at
- Oct 14, 2026, 12:17:03 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 14, 2026, 12:15:00 UTC
- First update from the server
- Oct 14, 2026, 12:16:18 UTC
- Completed
- Oct 14, 2026, 13:52:00 UTC
- Server deleted
- Oct 14, 2026, 13:52:00 UTC
- Cost of this run
- $0.051
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.