Reviewed measurements

Compare the evidence.

Two reports. The same workloads. Benchmark medians and separate network trials in view.

Selected plans
DigitalOceans-2vcpu-4gb
Vultrvc2-2c-4gb
Matching observed resources: x86_64 · 2 vCPU · 3.8 GiB RAMSource location: London, UK · same agent build and methodology.
CPU allocation
2 vCPU
2 vCPU
Observed memory
3.8 GiB
3.8 GiB
Processor
DO-Regular
Intel Core (Broadwell, no TSX, IBRS)
Location
London, UKlon1
London, UKLHR
List price
$24.00 / month$0.0357 / hour · before tax
$20.00 / month$0.027 / hour · before tax
OS / architecture
Ubuntu 24.04.5 LTS / x86_64
Ubuntu 24.04.5 LTS / x86_64
Sampling
1 deployment · 24h run skipped
1 deployment · 24h run skipped
Report date
17 Oct 2026
17 Oct 2026
Methodology
pilot-1 · AI-assisted review
pilot-1 · AI-assisted review
Each column is one deployment. Matching context does not establish equivalent physical hosts.Benchmark medians · network trials linked separately
PerformanceReviewed data
DigitalOcean2 vCPU · 3.8 GiB
Vultr2 vCPU · 3.8 GiB
01 /

CPU performance

sysbench prime events · max prime 20,000 · gzip level 6 · higher is better

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Single thread
352.0events/s88% of 400
330.4events/s83% of 400
All 2 vCPUs
694.1events/s87% of 800
659.5events/s82% of 800
gzip compression
160.7MiB/s80% of 200
145.0MiB/s72% of 200

Identical thread counts and test settings. Bars use a common scale within each row.

02 /

Memory bandwidth

sysbench · 256 MiB block · one thread · higher is better

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Read
5,527MiB/s55% of 10,000
9,007MiB/s90% of 10,000
Write
5,678MiB/s57% of 10,000
6,818MiB/s68% of 10,000

Bars share one scale across both rows. A memory copy workload is not part of this profile.

PerformanceReviewed data
DigitalOceanLondon, UK
VultrLondon, UK
03 /

Disk performance

fio · direct I/O · 1 MiB / QD32 sequential · 4 KiB / QD32 random

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Sequential read
3,485MB/s
387.0MB/s
Sequential write
1,476MB/s
362.1MB/s
Random read
55,405IOPS
61,079IOPS
Random write
33,344IOPS
40,182IOPS
Random read p95
1,090µs
905.2µs
Random write p95
1,974µs
1,036µs

Throughput and IOPS: higher is better. Latency: lower is better. Mixed 70/30 runs and p50/p99 latency are in each full report.

04 /

Network performance

LibreSpeed CLI · HTTPS / IPv4 · three streams · 10 seconds per direction

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Frankfurt · source
Network reportSeparate VM test · 17 Oct 2026, 17:13 UTCLondon, UK · Frankfurt, Germany (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 17:49 UTCLondon, UK · Frankfurt, Germany (Clouvider)
Frankfurt · Download
1,196Mbit/s
4,627Mbit/s
Frankfurt · Upload
771.4Mbit/s
1,017Mbit/s
Frankfurt · HTTP latency
17.3ms
14.9ms
Frankfurt · HTTP jitter
0.07ms
0.12ms
New York · source
Network reportSeparate VM test · 17 Oct 2026, 17:13 UTCLondon, UK · New York, United States (2) (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 17:49 UTCLondon, UK · New York, United States (2) (Clouvider)
New York · Download
816.4Mbit/s
1,123Mbit/s
New York · Upload
300.6Mbit/s
208.9Mbit/s
New York · HTTP latency
71.8ms
72.7ms
New York · HTTP jitter
0.12ms
2.38ms

Each network source is a linked same-VM supplement when available, otherwise a later test on a separate VM matching provider, plan, recorded region and resources. Frankfurt and New York are separate paths, with one trial per direction. HTTP latency and jitter are recorded; packet loss is not measured. Routes and times affect results; these trials do not establish maximum link capacity or long-term consistency.

PerformanceReviewed data
DigitalOcean2 vCPU · 3.8 GiB
Vultr2 vCPU · 3.8 GiB
05 /

PostgreSQL performance

PostgreSQL 16 · pgbench read/write · 4 clients · durability enabled

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
In-memory throughput
964.5transactions/s
2,073transactions/s
In-memory average latency
4.14ms
1.93ms
Storage-bound throughput
670.9transactions/s
1,581transactions/s
Storage-bound average latency
5.96ms
2.53ms

Both dataset profiles shown. This profile records average latency, not percentiles; read throughput and latency together.

06 /

Consistency over 24 hours

Separate 24-hour profile · hourly CPU, memory read and random disk read

Hourly repeat runsCPU · memory · disk
DigitalOcean
Not measured24-hour run skipped
Vultr
Not measured24-hour run skipped
No hourly samples exist for these reports, so no chart is drawn.Skipped runs are not scores.

No 24-hour consistency or long-term reliability is established.

07 /

Inspect the source reports.

Different workloads reveal different trade-offs. Every number links back to its test.