Reviewed measurements

Compare the evidence.

Two reports. The same workloads. Measured medians in view.

Selected plans

Vultrvoc-c-4c-8gb-75s-amd

Different resources selected: 4 vCPU · 7.7 GiB / 4 vCPU · 7.8 GiBSource location: Bangalore, IN · same agent build and methodology.

CPU allocation

4 vCPU

Observed memory

7.7 GiB

7.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

Sampling

1 deployment · 24h run skipped

Report date

17 Oct 2026

Methodology

pilot-1 · AI-assisted review

Report

View benchmark report

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

Single thread

1,357events/s90% of 1,500

497.5events/s33% of 1,500

All 4 vCPUs

5,421events/s90% of 6,000

1,544events/s26% of 6,000

gzip compression

181.6MiB/s73% of 250

241.3MiB/s97% 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

Read

15,482MiB/s77% of 20,000

8,331MiB/s42% of 20,000

Write

15,572MiB/s78% of 20,000

8,450MiB/s42% of 20,000

Bars share one scale across both rows. A memory copy workload is not part of this profile.

PerformanceReviewed data

VultrBangalore, IN

DigitalOceanBangalore, IN

03 /

Disk performance

fio · direct I/O · 1 MiB / QD32 sequential · 4 KiB / QD32 random

Sequential read

4,320MB/s

9,489MB/s

Sequential write

3,181MB/s

1,670MB/s

Random read

98,509IOPS

151,801IOPS

Random write

80,273IOPS

135,456IOPS

Random read p95

428.0µs

280.6µs

Random write p95

536.6µs

329.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

Download · endpoint 1

99.8Mbit/s

99.9Mbit/s

Download · endpoint 2

99.9Mbit/s

Upload · endpoint 1

97.3Mbit/s

97.5Mbit/s

Upload · endpoint 2

95.5Mbit/s

97.1Mbit/s

Latency · endpoint 1

141.3ms

131.2ms

Latency · endpoint 2

252.4ms

147.1ms

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.

PerformanceReviewed data

Vultr4 vCPU · 7.7 GiB

DigitalOcean4 vCPU · 7.8 GiB

05 /

PostgreSQL performance

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

In-memory throughput

3,737transactions/s

4,779transactions/s

In-memory average latency

1.07ms

0.84ms

Storage-bound throughput

3,280transactions/s

3,910transactions/s

Storage-bound average latency

1.22ms

1.02ms

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.

Full reviewed results and limits for each report.

Vultr report

Report JSONEvidence and limits

DigitalOcean report

Report JSONEvidence and limits

Different workloads reveal different trade-offs. Every number links back to its test.