Reviewed measurements

Compare the evidence.

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

Selected plans
Vultrvc2-2c-4gb
DigitalOceans-2vcpu-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
Intel Core (Broadwell, no TSX, IBRS)
DO-Regular
Location
London, UKLHR
London, UKlon1
List price
$20.00 / month$0.027 / hour · before tax
$24.00 / month$0.0357 / 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
Vultr2 vCPU · 3.8 GiB
DigitalOcean2 vCPU · 3.8 GiB
01 /

CPU performance

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

MetricVultr vc2-2c-4gbDigitalOcean s-2vcpu-4gb
Single thread
317.6events/s79% of 400
321.6events/s80% of 400
All 2 vCPUs
622.7events/s78% of 800
626.7events/s78% of 800
gzip compression
144.8MiB/s72% of 200
160.8MiB/s80% 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

MetricVultr vc2-2c-4gbDigitalOcean s-2vcpu-4gb
Read
8,310MiB/s83% of 10,000
5,611MiB/s56% of 10,000
Write
6,316MiB/s63% of 10,000
5,829MiB/s58% of 10,000

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

PerformanceReviewed data
VultrLondon, UK
DigitalOceanLondon, UK
03 /

Disk performance

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

MetricVultr vc2-2c-4gbDigitalOcean s-2vcpu-4gb
Sequential read
373.1MB/s
4,099MB/s
Sequential write
360.3MB/s
839.1MB/s
Random read
57,197IOPS
58,495IOPS
Random write
38,913IOPS
43,499IOPS
Random read p95
946.2µs
823.3µs
Random write p95
1,106µs
1,221µ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

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

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
Vultr2 vCPU · 3.8 GiB
DigitalOcean2 vCPU · 3.8 GiB
05 /

PostgreSQL performance

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

MetricVultr vc2-2c-4gbDigitalOcean s-2vcpu-4gb
In-memory throughput
1,870transactions/s
1,479transactions/s
In-memory average latency
2.14ms
2.70ms
Storage-bound throughput
1,484transactions/s
1,246transactions/s
Storage-bound average latency
2.69ms
3.21ms

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
Vultr
Not measured24-hour run skipped
DigitalOcean
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.