Reviewed measurements

Compare the evidence.

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

Selected plans

Vultrvc2-2c-4gb

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

CPU allocation

2 vCPU

Observed memory

3.8 GiB

Processor

DO-Regular

Intel Core (Broadwell, no TSX, IBRS)

Location

London, UKlon1

London, UKLHR

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

DigitalOcean2 vCPU · 3.8 GiB

Vultr2 vCPU · 3.8 GiB

01 /

CPU performance

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

Single thread

788.5events/s99% of 800

330.4events/s41% of 800

All 2 vCPUs

1,546events/s77% of 2,000

659.5events/s33% of 2,000

gzip compression

124.9MiB/s83% of 150

145.0MiB/s97% of 150

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

9,144MiB/s91% of 10,000

9,007MiB/s90% of 10,000

Write

7,351MiB/s74% of 10,000

6,818MiB/s68% of 10,000

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

PerformanceReviewed data

DigitalOceanLondon, UK

VultrLondon, UK

03 /

Disk performance

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

Sequential read

10,626MB/s

387.0MB/s

Sequential write

1,587MB/s

362.1MB/s

Random read

76,483IOPS

61,079IOPS

Random write

57,484IOPS

40,182IOPS

Random read p95

585.7µs

905.2µs

Random write p95

790.5µs

1,036µ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

100.1Mbit/s

Download · endpoint 2

100.1Mbit/s

Upload · endpoint 1

100.1Mbit/s

Upload · endpoint 2

100.1Mbit/s

Latency · endpoint 1

0.79ms

2.95ms

Latency · endpoint 2

2.30ms

0.42ms

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

DigitalOcean2 vCPU · 3.8 GiB

Vultr2 vCPU · 3.8 GiB

05 /

PostgreSQL performance

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

In-memory throughput

2,348transactions/s

2,073transactions/s

In-memory average latency

1.70ms

1.93ms

Storage-bound throughput

1,490transactions/s

1,581transactions/s

Storage-bound average latency

2.68ms

2.53ms

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

DigitalOcean

Not measured24-hour run skipped

Vultr

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.

DigitalOcean report

Report JSONEvidence and limits

Vultr report

Report JSONEvidence and limits

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