Reviewed measurements

Compare the evidence.

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

Selected plans
Vultrvoc-c-4c-8gb-75s-amd
DigitalOceanc-4
Different resources selected: 4 vCPU · 7.7 GiB / 4 vCPU · 7.8 GiBSource location: London, UK · same agent build and methodology.
CPU allocation
4 vCPU
4 vCPU
Observed memory
7.7 GiB
7.8 GiB
Processor
AMD EPYC-Milan
Intel Xeon Platinum 8280 @ 2.70GHz
Location
London, UKLHR
London, UKlon1
List price
$80.00 / month$0.110 / hour · before tax
$84.00 / month$0.125 / 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
Vultr4 vCPU · 7.7 GiB
DigitalOcean4 vCPU · 7.8 GiB
01 /

CPU performance

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

MetricVultr voc-c-4c-8gb-75s-amdDigitalOcean c-4
Single thread
1,667events/s83% of 2,000
458.3events/s23% of 2,000
All 4 vCPUs
6,643events/s83% of 8,000
1,435events/s18% of 8,000
gzip compression
241.8MiB/s97% of 250
207.0MiB/s83% of 250

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 voc-c-4c-8gb-75s-amdDigitalOcean c-4
Read
34,011MiB/s85% of 40,000
7,433MiB/s19% of 40,000
Write
24,907MiB/s62% of 40,000
8,267MiB/s21% of 40,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 voc-c-4c-8gb-75s-amdDigitalOcean c-4
Sequential read
6,823MB/s
8,795MB/s
Sequential write
2,998MB/s
1,685MB/s
Random read
115,232IOPS
130,395IOPS
Random write
96,493IOPS
108,809IOPS
Random read p95
362.5µs
354.3µs
Random write p95
460.8µs
469.0µ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 voc-c-4c-8gb-75s-amdDigitalOcean c-4
Frankfurt · source
Network reportSeparate VM test · 17 Oct 2026, 17:52 UTCLondon, UK · Frankfurt, Germany (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 18:12 UTCLondon, UK · Frankfurt, Germany (Clouvider)
Frankfurt · Download
1,518Mbit/s
869.0Mbit/s
Frankfurt · Upload
1,013Mbit/s
914.6Mbit/s
Frankfurt · HTTP latency
12.2ms
16.0ms
Frankfurt · HTTP jitter
0.15ms
0.09ms
New York · source
Network reportSeparate VM test · 17 Oct 2026, 17:52 UTCLondon, UK · New York, United States (2) (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 18:12 UTCLondon, UK · New York, United States (2) (Clouvider)
New York · Download
1,182Mbit/s
909.5Mbit/s
New York · Upload
228.7Mbit/s
302.2Mbit/s
New York · HTTP latency
71.4ms
71.8ms
New York · HTTP jitter
0.06ms
0.20ms

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

PostgreSQL performance

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

MetricVultr voc-c-4c-8gb-75s-amdDigitalOcean c-4
In-memory throughput
4,473transactions/s
4,224transactions/s
In-memory average latency
0.89ms
0.95ms
Storage-bound throughput
3,678transactions/s
3,518transactions/s
Storage-bound average latency
1.09ms
1.14ms

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.