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-2c-4gb-50s-amd Change Vultr voc-c-2c-4gb-50s-amd Add a plan Compare up to three Matching observed resources: x86_64 · 2 vCPU · 3.8 GiB RAM Source location: Bangalore, IN · same agent build and methodology.
CPU allocation
2 vCPU
2 vCPU
Observed memory
3.8 GiB
3.8 GiB
Processor
AMD EPYC-Rome
Intel Xeon Platinum 8280 @ 2.70GHz
Location
Bangalore, INBLR
Bangalore, INblr1
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 2 vCPU · 3.8 GiB
01 /
CPU performance sysbench prime events · max prime 20,000 · gzip level 6 · higher is better
Metric Vultr voc-c-2c-4gb-50s-amd DigitalOcean c2-2vcpu-4gb
Single thread
1,361 events/s
91% of 1,500 470.9 events/s
31% of 1,500
All 2 vCPUs
2,693 events/s
90% of 3,000 737.5 events/s
25% of 3,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 Vultr voc-c-2c-4gb-50s-amd DigitalOcean c2-2vcpu-4gb
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 Vultr voc-c-2c-4gb-50s-amd DigitalOcean c2-2vcpu-4gb
Sequential read
3,359 MB/s
8,759 MB/s
Sequential write
2,222 MB/s
1,730 MB/s
Random read
101,699 IOPS
145,439 IOPS
Random write
80,346 IOPS
123,920 IOPS
Random read p95
411.6 µs
284.7 µs
Random write p95
528.4 µs
370.7 µ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 Vultr voc-c-2c-4gb-50s-amd DigitalOcean c2-2vcpu-4gb
Download · endpoint 1
99.9 Mbit/s
99.9 Mbit/s
Download · endpoint 2
99.9 Mbit/s
99.9 Mbit/s
Upload · endpoint 1
97.5 Mbit/s
97.6 Mbit/s
Upload · endpoint 2
95.5 Mbit/s
97.4 Mbit/s
Latency · endpoint 1
146.1 ms
132.2 ms
Latency · endpoint 2
251.5 ms
156.5 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 2 vCPU · 3.8 GiB
05 /
PostgreSQL performance PostgreSQL 16 · pgbench read/write · 4 clients · durability enabled
Metric Vultr voc-c-2c-4gb-50s-amd DigitalOcean c2-2vcpu-4gb
In-memory throughput
2,041 transactions/s
3,048 transactions/s
In-memory average latency
1.96 ms
1.31 ms
Storage-bound throughput
2,479 transactions/s
2,437 transactions/s
Storage-bound average latency
1.61 ms
1.64 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.