Compare the evidence. Two reports. The same workloads. Measured medians in view.
Share comparison Download CSV Jump to: CPU Memory Disk Network PostgreSQL Selected plans
Vultr voc-c-4c-8gb-75s-amd Change Vultr voc-c-4c-8gb-75s-amd Add a plan Compare up to three Different resources selected: 4 vCPU · 7.8 GiB / 4 vCPU · 7.7 GiB Source location: Bangalore, IN · same agent build and methodology.
CPU allocation
4 vCPU
4 vCPU
Observed memory
7.8 GiB
7.7 GiB
Processor
DO-Regular
AMD EPYC-Rome
Location
Bangalore, INblr1
Bangalore, INBLR
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
Performance Reviewed data
DigitalOcean 4 vCPU · 7.8 GiB
01 /
CPU performance sysbench prime events · max prime 20,000 · gzip level 6 · higher is better
Metric DigitalOcean s-4vcpu-8gb Vultr voc-c-4c-8gb-75s-amd
Single thread
360.3 events/s
24% of 1,500 1,333 events/s
89% of 1,500
All 4 vCPUs
1,444 events/s
24% of 6,000 5,299 events/s
88% of 6,000
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
Metric DigitalOcean s-4vcpu-8gb Vultr voc-c-4c-8gb-75s-amd
Bars share one scale across both rows. A memory copy workload is not part of this profile.
Performance Reviewed data
DigitalOcean Bangalore, IN
03 /
Disk performance fio · direct I/O · 1 MiB / QD32 sequential · 4 KiB / QD32 random
Metric DigitalOcean s-4vcpu-8gb Vultr voc-c-4c-8gb-75s-amd
Sequential read
4,585 MB/s
3,421 MB/s
Sequential write
2,212 MB/s
2,410 MB/s
Random read
84,421 IOPS
92,339 IOPS
Random write
61,228 IOPS
79,365 IOPS
Random read p95
585.7 µs
473.1 µs
Random write p95
880.6 µs
593.9 µ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
Metric DigitalOcean s-4vcpu-8gb Vultr voc-c-4c-8gb-75s-amd
Download · endpoint 1
99.9 Mbit/s
92.3 Mbit/s
Download · endpoint 2
14.7 Mbit/s
99.9 Mbit/s
Upload · endpoint 1
97.5 Mbit/s
97.4 Mbit/s
Upload · endpoint 2
29.5 Mbit/s
95.5 Mbit/s
Latency · endpoint 1
131.2 ms
152.7 ms
Latency · endpoint 2
163.5 ms
247.7 ms
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.
Performance Reviewed data
DigitalOcean 4 vCPU · 7.8 GiB
05 /
PostgreSQL performance PostgreSQL 16 · pgbench read/write · 4 clients · durability enabled
Metric DigitalOcean s-4vcpu-8gb Vultr voc-c-4c-8gb-75s-amd
In-memory throughput
2,807 transactions/s
2,670 transactions/s
In-memory average latency
1.42 ms
1.50 ms
Storage-bound throughput
2,459 transactions/s
1,920 transactions/s
Storage-bound average latency
1.62 ms
2.08 ms
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 runs CPU · memory · disk
Not measured 24-hour run skipped
Not measured 24-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. Full reviewed results and limits for each report.