Reviewed measurements

Compare the evidence.

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

Selected plans
DigitalOceans-4vcpu-8gb
Vultrvc2-4c-8gb
Different resources selected: 4 vCPU · 7.8 GiB / 4 vCPU · 7.7 GiBSource location: London, UK · same agent build and methodology.
CPU allocation
4 vCPU
4 vCPU
Observed memory
7.8 GiB
7.7 GiB
Processor
DO-Regular
Intel Xeon (Skylake, IBRS)
Location
London, UKlon1
London, UKLHR
List price
$48.00 / month$0.0714 / hour · before tax
$40.00 / month$0.055 / 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
DigitalOcean4 vCPU · 7.8 GiB
Vultr4 vCPU · 7.7 GiB
01 /

CPU performance

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

MetricDigitalOcean s-4vcpu-8gbVultr vc2-4c-8gb
Single thread
339.5events/s68% of 500
421.1events/s84% of 500
All 4 vCPUs
1,263events/s63% of 2,000
1,634events/s82% of 2,000
gzip compression
144.8MiB/s72% of 200
181.0MiB/s91% 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-4vcpu-8gbVultr vc2-4c-8gb
Read
5,332MiB/s53% of 10,000
8,586MiB/s86% of 10,000
Write
5,525MiB/s55% of 10,000
8,358MiB/s84% 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-4vcpu-8gbVultr vc2-4c-8gb
Sequential read
3,959MB/s
552.8MB/s
Sequential write
1,774MB/s
507.5MB/s
Random read
75,993IOPS
90,080IOPS
Random write
47,558IOPS
49,710IOPS
Random read p95
634.9µs
440.3µs
Random write p95
1,057µs
872.4µ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-4vcpu-8gbVultr vc2-4c-8gb
Frankfurt · source
Network reportSeparate VM test · 17 Oct 2026, 17:26 UTCLondon, UK · Frankfurt, Germany (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 17:11 UTCLondon, UK · Frankfurt, Germany (Clouvider)
Frankfurt · Download
1,220Mbit/s
2,513Mbit/s
Frankfurt · Upload
1,005Mbit/s
1,033Mbit/s
Frankfurt · HTTP latency
17.5ms
12.5ms
Frankfurt · HTTP jitter
0.09ms
0.07ms
New York · source
Network reportSeparate VM test · 17 Oct 2026, 17:26 UTCLondon, UK · New York, United States (2) (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 17:11 UTCLondon, UK · New York, United States (2) (Clouvider)
New York · Download
815.2Mbit/s
1,149Mbit/s
New York · Upload
290.3Mbit/s
227.1Mbit/s
New York · HTTP latency
71.6ms
71.9ms
New York · HTTP jitter
0.06ms
0.09ms

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
DigitalOcean4 vCPU · 7.8 GiB
Vultr4 vCPU · 7.7 GiB
05 /

PostgreSQL performance

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

MetricDigitalOcean s-4vcpu-8gbVultr vc2-4c-8gb
In-memory throughput
3,354transactions/s
3,431transactions/s
In-memory average latency
1.19ms
1.16ms
Storage-bound throughput
2,305transactions/s
2,712transactions/s
Storage-bound average latency
1.73ms
1.47ms

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.