Reviewed measurements

Compare the evidence.

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

Selected plans

Vultrvoc-c-2c-4gb-50s-amd

Matching observed resources: x86_64 · 2 vCPU · 3.8 GiB RAMSource location: Bangalore, IN · same agent build and methodology.

CPU allocation

2 vCPU

Observed memory

3.8 GiB

Processor

AMD EPYC-Rome

Intel Xeon Platinum 8280 @ 2.70GHz

Location

Bangalore, INBLR

Bangalore, INblr1

List price

$40.00 / month$0.055 / hour · before tax

$47.00 / month$0.0699 / hour · before tax

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.Benchmark medians · network trials linked separately

PerformanceReviewed data

Vultr2 vCPU · 3.8 GiB

DigitalOcean2 vCPU · 3.8 GiB

01 /

CPU performance

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

Single thread

1,317events/s88% of 1,500

470.9events/s31% of 1,500

All 2 vCPUs

2,652events/s88% of 3,000

737.5events/s25% of 3,000

gzip compression

181.6MiB/s73% of 250

207.2MiB/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

Read

15,716MiB/s79% of 20,000

9,536MiB/s48% of 20,000

Write

13,754MiB/s69% of 20,000

10,177MiB/s51% 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

2,211MB/s

8,759MB/s

Sequential write

2,023MB/s

1,730MB/s

Random read

94,688IOPS

145,439IOPS

Random write

78,403IOPS

123,920IOPS

Random read p95

452.6µs

284.7µs

Random write p95

544.8µ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

LibreSpeed CLI · HTTPS / IPv4 · three streams · 10 seconds per direction

Frankfurt · source

Network reportSeparate VM test · 17 Oct 2026, 17:48 UTCBangalore, IN · Frankfurt, Germany (Clouvider)

Network reportSeparate VM test · 17 Oct 2026, 18:10 UTCBangalore, IN · Frankfurt, Germany (Clouvider)

Frankfurt · Download

267.7Mbit/s

412.7Mbit/s

Frankfurt · Upload

76.0Mbit/s

148.0Mbit/s

Frankfurt · HTTP latency

173.3ms

130.9ms

Frankfurt · HTTP jitter

0.09ms

0.18ms

New York · source

Network reportSeparate VM test · 17 Oct 2026, 17:48 UTCBangalore, IN · New York, United States (2) (Clouvider)

Network reportSeparate VM test · 17 Oct 2026, 18:10 UTCBangalore, IN · New York, United States (2) (Clouvider)

New York · Download

139.6Mbit/s

247.5Mbit/s

New York · Upload

39.4Mbit/s

60.9Mbit/s

New York · HTTP latency

300.8ms

218.0ms

New York · HTTP jitter

0.77ms

0.05ms

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

Vultr2 vCPU · 3.8 GiB

DigitalOcean2 vCPU · 3.8 GiB

05 /

PostgreSQL performance

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

In-memory throughput

1,956transactions/s

3,048transactions/s

In-memory average latency

2.04ms

1.31ms

Storage-bound throughput

1,462transactions/s

2,437transactions/s

Storage-bound average latency

2.73ms

1.64ms

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.