Each column is one deployment. Matching context does not establish equivalent physical hosts.Reviewed data · within-run medians
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 vc2-4c-8gbDigitalOcean c-4
Single thread
420.3events/s
84% of 500
458.3events/s
92% of 500
All 4 vCPUs
1,662events/s
83% of 2,000
1,435events/s
72% of 2,000
gzip compression
180.6MiB/s
72% of 250
207.0MiB/s
83% 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 vc2-4c-8gbDigitalOcean c-4
Read
8,432MiB/s
84% of 10,000
7,433MiB/s
74% of 10,000
Write
8,455MiB/s
85% of 10,000
8,267MiB/s
83% 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-4c-8gbDigitalOcean c-4
Sequential read
539.3MB/s
8,795MB/s
Sequential write
484.9MB/s
1,685MB/s
Random read
86,151IOPS
130,395IOPS
Random write
51,114IOPS
108,809IOPS
Random read p95
444.4µs
354.3µs
Random write p95
749.6µ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
Same two controlled London endpoints · one iperf3 stream · 100 Mbit/s rate setting
MetricVultr vc2-4c-8gbDigitalOcean c-4
Download · endpoint 1
100.1Mbit/s
100.1Mbit/s
Download · endpoint 2
100.1Mbit/s
100.1Mbit/s
Upload · endpoint 1
100.1Mbit/s
100.1Mbit/s
Upload · endpoint 2
100.2Mbit/s
100.1Mbit/s
Latency · endpoint 1
3.63ms
0.63ms
Latency · endpoint 2
0.41ms
2.40ms
Source location affects latency. Actual bytes can exceed the 64 MiB target; these routes do not measure maximum link capacity. Jitter and packet loss are not reported.