Skip to main content

DigitalOcean Basic 2 vCPU / 2 GB

San Francisco 3

Benchmark complete
Finished Oct 12, 2026
Geekbench 7 single-core
763
Faster than 22% of 2 vCPU plans
Geekbench 7 multi-core
Skipped
Disk 4K IOPS
67,776
fio random read and write, 50/50
Monthly price at test time
$18.00
Same price today

Server

  • Provider
    DigitalOcean
  • Plan
    Basic 2 vCPU / 2 GB
  • Location
    San Francisco 3
  • vCPU
    2
  • RAM
    2 GB
  • Storage
    60 GB SSD
  • Network
    2 Gbps
  • OS image
    ubuntu-24-04-x64
  • Trigger
    Scheduled
  • Queued at
    Oct 12, 2026, 11:24:00 UTC
Visit DigitalOcean

Referral link. If you sign up through it, I may get paid. How this works

CPU

Version Single-core Multi-core
Geekbench 7 763 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
695
121st of 129
Single-core only
Navigation
929
115th of 129
Single-core only
HTML5 Browser
817
110th of 129
Single-core only
PDF Viewer
671
124th of 129
Single-core only
Photo Library
682
111th of 129
Single-core only
Clang
773
113th of 129
Single-core only
Text Processing
614
118th of 129
Single-core only
Asset Compression
678
120th of 129
Single-core only
HDR
725
116th of 129
Single-core only
Photo Editor
852
100th of 129
Single-core only
Ray Tracer
813
114th of 129
Single-core only
Structure from Motion
917
104th of 129
Single-core only
Game Physics
689
119th of 129
Single-core only
Video Encoder
724
112th of 129
Single-core only
Audio Encoder
853
113th of 129
Single-core only
Video Player
860
101st of 129
Single-core only

Rank among the 129 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 41.6 GB/s 3 1.2%
Scale higher is better 23 GB/s 3 0.967%
Add higher is better 26.1 GB/s 3 2.31%
Triad higher is better 25.9 GB/s 3 3.05%

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 290/s 3 4.66%
RSA 4096 verifies higher is better 18,977/s 3 0.187%
SHA-256 higher is better 346 MB/s 3 1.08%
AES-256-GCM higher is better 6.11 GB/s 3 15.8%
ChaCha20-Poly1305 higher is better 2.65 GB/s 3 1.09%

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.67 ms 3 3.96%
Requests per second, 90th percentile higher is better 338/s 3 3%
Request latency, 99.9th percentile lower is better 15.2 ms 3 4.61%
Requests per second, average higher is better 302/s 3 3.04%

Average of 3 runs. Spread is the standard deviation as a share of the average.

Disk

Block size Read Write Total
4K 132.2 MB/s (33,843 IOPS) 132.6 MB/s (33,933 IOPS) 264.8 MB/s (67,776 IOPS)
64K 643.8 MB/s (10,300 IOPS) 647.1 MB/s (10,354 IOPS) 1.26 GB/s (20,654 IOPS)
512K 908.1 MB/s (1,816 IOPS) 956.3 MB/s (1,912 IOPS) 1.82 GB/s (3,728 IOPS)
1M 898.9 MB/s (898 IOPS) 958.7 MB/s (958 IOPS) 1.81 GB/s (1,856 IOPS)

fio random read and write, 50/50, run by YABS against the boot disk.

Network

IPv4 transfer speed

Loading...
Target Protocol Send Receive
Clouvider, London, UK (10G) IPv4 1.27 Gbps 1.61 Gbps
Eranium, Amsterdam, NL (100G) IPv4 1.29 Gbps 1.65 Gbps
Leaseweb, Singapore, SG (10G) IPv4 841 Mbps 1.32 Gbps
Clouvider, Los Angeles, CA, US (10G) IPv4 2 Gbps 1.88 Gbps
Leaseweb, NYC, NY, US (10G) IPv4 1.81 Gbps 1.46 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,590 0.218 ms
fdatasync 3,368 0.297 ms
fsync 1,147 0.872 ms
fsync_writethrough Not supported here n/a
open_sync 1,443 0.693 ms
Two 8 kB writes
open_datasync 2,443 0.409 ms
fdatasync 4,376 0.229 ms
fsync 1,202 0.832 ms
fsync_writethrough Not supported here n/a
open_sync 743 1.35 ms
open_sync at different write sizes
1 * 16kB open_sync write 1,514 0.66 ms
2 * 8kB open_sync writes 680 1.47 ms
4 * 4kB open_sync writes 336 2.98 ms
8 * 2kB open_sync writes 170 5.87 ms
16 * 1kB open_sync writes 114 8.79 ms
fsync on a non-write descriptor
write, fsync, close 1,201 0.833 ms
write, close, fsync 1,553 0.644 ms
Non-synced 8 kB writes
write 699,068 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,283 0.712 ms 1.16 ms 2.07 ms 7.59 ms 0
Read/write (TPC-B like) 8 2,901 2.45 ms 4.89 ms 7.94 ms 21.3 ms 0
Read/write (TPC-B like) 32 2,533 10.1 ms 29.3 ms 50.1 ms 87.2 ms 0
Read only 1 22,747 0.04 ms 0.067 ms 0.09 ms 0.206 ms 0
Read only 8 33,010 0.217 ms 0.393 ms 0.509 ms 1.19 ms 0
Read only 32 31,065 0.861 ms 1.67 ms 2.25 ms 4.53 ms 0

Scale 10 (1,000,000 accounts), loaded in 1.85 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 783 1.15 ms 2.09 ms 4.03 ms 7.38 ms 0
Read/write (TPC-B like) 8 2,354 3.13 ms 5.97 ms 9.14 ms 18.4 ms 0
Read/write (TPC-B like) 32 2,636 11.3 ms 19.5 ms 26.1 ms 43 ms 0
Read only 1 4,691 0.202 ms 0.442 ms 0.909 ms 1.92 ms 0
Read only 8 18,324 0.355 ms 0.906 ms 1.59 ms 3.26 ms 0
Read only 32 18,022 1.48 ms 3.27 ms 5.01 ms 9.02 ms 0

Scale 100 (10,000,000 accounts), loaded in 22.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 185 3,690 5 ms 8.13 ms 15 ms 0
Read/write 8 507 10,149 14.7 ms 25.7 ms 35 ms 0
Read/write 32 536 10,720 57.9 ms 105 ms 132 ms 0
Read only 1 473 7,562 1.86 ms 3.82 ms 7.57 ms 0
Read only 8 1,100 17,598 7.04 ms 10.8 ms 13 ms 0
Read only 32 945 15,118 32.5 ms 48.3 ms 57.9 ms 0

10 tables of 100,000 rows, loaded in 13.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 49,346 44,860 1.07 ms 3.41 ms 6.24 ms
1:1 set:get 45,781 22,890 1.17 ms 4.1 ms 7.87 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 209 908 1,245 4.64 s
Express express-postgresjs 4,893 6,424 22,531 118 ms
Fastify fastify-postgres 5,117 6,865 23,739 101 ms
NestJS nestjs 3,122 3,299 12,902 160 ms
Nuxt nuxt 4,640 7,483 19,697 403 ms
FastAPI fastapi 2,346 3,088 11,314 482 ms
Django django-postgresql 738 812 2,180 439 ms
Rails rails 1,216 1,719 7,564 344 ms
Laravel laravel 450 454 879 640 ms
Symfony symfony 533 600 1,785 579 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.24 1.25 s 1.73 s 1.79 s 0%
Shop page 1.24 1.72 s 2.14 s 2.41 s 0%
Category page 1.24 1.04 s 1.66 s 1.89 s 0%
Product page 1.24 1.1 s 1.47 s 1.72 s 0%
Product search 1.24 947 ms 1.31 s 1.37 s 0%
32 virtual users
Home page 1.35 4.97 s 5.73 s 5.99 s 0%
Shop page 1.35 6.29 s 7.47 s 7.57 s 0%
Category page 1.34 5.11 s 6.45 s 7.01 s 0%
Product page 1.01 4.44 s 5.24 s 5.41 s 0%
Product search 0.901 4.73 s 5.32 s 5.43 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 2.15 1.39 s 3.05 s 4.23 s 0%
Cart 2.15 1.1 s 1.48 s 1.72 s 0%
Checkout 2.15 828 ms 1.12 s 1.37 s 0%
32 virtual users
Add to cart 2.25 4.72 s 6.01 s 7.33 s 0%
Cart 2.25 5.23 s 6.39 s 7.05 s 0%
Checkout 2.07 4 s 4.78 s 4.91 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 0.945 466 ms 608 ms 730 ms 0%
Topic JSON 0.489 238 ms 284 ms 323 ms 0%
Home page 0.489 424 ms 475 ms 496 ms 0%
Categories page 0.244 489 ms 539 ms 544 ms 0%
User activity page 0.228 281 ms 449 ms 510 ms 0%
4 virtual users
Topic page 1.7 1.02 s 1.34 s 1.77 s 0%
Topic JSON 0.86 573 ms 704 ms 842 ms 0%
Home page 0.827 877 ms 1.13 s 1.2 s 0%
Categories page 0.454 1.13 s 1.52 s 2.25 s 0%
User activity page 0.422 594 ms 751 ms 782 ms 0%
16 virtual users
Topic page 1.6 2.12 s 3 s 3.2 s 0%
Topic JSON 0.825 1.72 s 2.24 s 2.4 s 0%
Home page 0.809 2.07 s 2.69 s 2.84 s 0%
Categories page 0.413 2.15 s 2.84 s 2.92 s 0%
User activity page 0.428 1.75 s 2.58 s 2.64 s 0%

Anonymous

Step Requests/s Median p95 p99 Error rate
16 virtual users
Topic page 34.6 133 ms 282 ms 477 ms 0%
Topic JSON 17.4 130 ms 293 ms 468 ms 0%
Home page 17.4 132 ms 301 ms 473 ms 0%
Categories page 8.66 137 ms 302 ms 577 ms 0%
User activity page 8.69 398 ms 717 ms 936 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 484 MB of it. The container peaked at 1,483 MB.

Ghost

Readers

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 4.15 69 ms 91 ms 127 ms 0%
Post page 10.3 37.1 ms 46.9 ms 59.8 ms 0%
Tag page 2.08 45.1 ms 57.3 ms 61.7 ms 0%
Author page 2.06 46.7 ms 60.1 ms 69 ms 0%
RSS feed 2.06 51.1 ms 66.8 ms 74.5 ms 0%
4 virtual users
Home page 5.32 202 ms 288 ms 348 ms 0%
Post page 13.3 132 ms 202 ms 262 ms 0%
Tag page 2.68 118 ms 182 ms 232 ms 0%
Author page 2.66 130 ms 203 ms 223 ms 0%
RSS feed 2.66 139 ms 222 ms 277 ms 0%
16 virtual users
Home page 5.36 739 ms 944 ms 993 ms 0%
Post page 13.4 625 ms 811 ms 873 ms 0%
Tag page 2.68 409 ms 533 ms 612 ms 0%
Author page 2.66 387 ms 543 ms 591 ms 0%
RSS feed 2.66 424 ms 562 ms 687 ms 0%

Staff in Ghost Admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Post list 2.09 68.1 ms 90.8 ms 160 ms 0%
Post editor 6.29 27.9 ms 41.1 ms 56.1 ms 0%
Saving a draft 6.29 72.3 ms 97.1 ms 141 ms 0%
Member list 2.09 77.6 ms 106 ms 147 ms 0%
4 virtual users
Post list 2.67 91.8 ms 123 ms 150 ms 0%
Post editor 8.08 48.8 ms 68.4 ms 155 ms 0%
Saving a draft 8.12 363 ms 482 ms 531 ms 0%
Member list 2.72 97.6 ms 133 ms 154 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 344 MB and MySQL at 580 MB.

Wagtail

Visitors

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 0.791 165 ms 196 ms 235 ms 0%
Blog index 0.791 592 ms 674 ms 708 ms 0%
Blog post 2.34 53.4 ms 78.9 ms 90 ms 0%
Bread page 2.36 56.3 ms 66.8 ms 76.5 ms 0%
Location page 0.791 52.1 ms 64.3 ms 69.3 ms 0%
Site search 0.775 93.8 ms 157 ms 169 ms 0%
4 virtual users
Home page 1.38 440 ms 595 ms 619 ms 0%
Blog index 1.4 1.4 s 1.9 s 2.12 s 0%
Blog post 4.16 110 ms 197 ms 240 ms 0%
Bread page 4.18 129 ms 195 ms 240 ms 0%
Location page 1.41 111 ms 172 ms 231 ms 0%
Site search 1.38 187 ms 389 ms 459 ms 0%
16 virtual users
Home page 1.12 1.6 s 2.26 s 2.54 s 0%
Blog index 1.21 3.88 s 5.65 s 6.16 s 0%
Blog post 3.4 883 ms 1.56 s 2.05 s 0%
Bread page 3.41 899 ms 1.6 s 1.88 s 0%
Location page 1.18 912 ms 1.52 s 1.71 s 0%
Site search 1.13 1.07 s 1.64 s 2.16 s 0%

Editors in the Wagtail admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Admin dashboard 0.338 182 ms 209 ms 244 ms 0%
Page explorer 0.693 649 ms 850 ms 950 ms 0%
Page editor 1.01 316 ms 383 ms 480 ms 0%
Image library 0.338 122 ms 150 ms 1.18 s 0%
Admin page search 0.338 70.3 ms 160 ms 166 ms 0%
4 virtual users
Admin dashboard 0.552 424 ms 870 ms 931 ms 0%
Page explorer 1.17 1.64 s 2.39 s 2.5 s 0%
Page editor 1.74 725 ms 1.31 s 1.5 s 0%
Image library 0.584 406 ms 764 ms 808 ms 0%
Admin page search 0.552 160 ms 481 ms 600 ms 0%

k6 with a fixed number of virtual users, 61 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 293 MB, Postgres at 178 MB, and Redis at 26 MB.

Advertised vs. measured

Advertised Measured
vCPU 2 2
CPU Shared vCPU 2% of busy CPU time stolen
RAM 2 GB 1.9 GiB
Storage 60 GB SSD 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-Regular
CPU cores
2
CPU frequency
1995 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
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 2 vCPU / 2 GB
Product line
Basic
Location
San Francisco 3
vCPU
2 shared vCPU
Architecture
x86_64
RAM
2 GB
Storage
60 GB SSD
Virtualization
KVM
Network
2 Gbps
Transfer
3 TB
Port 25
Closed
Monthly price at test time
$18.00
Hourly price at test time
$0.027
YABS version
v2026-09-20
Ran at
Oct 12, 2026, 11:25:41 UTC
Parser version
5

Run timeline

Queued
Oct 12, 2026, 11:24:00 UTC
First update from the server
Oct 12, 2026, 11:25:31 UTC
Completed
Oct 12, 2026, 13:03:00 UTC
Server deleted
Oct 12, 2026, 13:03:00 UTC
Cost of this run
$0.044
Watch party 0 watching

This party closed at . It's read only now.

Watch party

Loading the party