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
Add a plan Compare up to three Matching observed resources: x86_64 · 2 vCPU · 3.8 GiB RAM Source location: London, UK · same agent build and methodology.
CPU allocation
2 vCPU
2 vCPU
Observed memory
3.8 GiB
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
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 DigitalOcean s-2vcpu-4gb Vultr vc2-2c-4gb
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-2vcpu-4gb Vultr vc2-2c-4gb
Bars share one scale across both rows. A memory copy workload is not part of this profile.
03 /
Disk performance fio · direct I/O · 1 MiB / QD32 sequential · 4 KiB / QD32 random
Metric DigitalOcean s-2vcpu-4gb Vultr vc2-2c-4gb
Sequential read
4,099 MB/s
387.0 MB/s
Sequential write
839.1 MB/s
362.1 MB/s
Random read
58,495 IOPS
61,079 IOPS
Random write
43,499 IOPS
40,182 IOPS
Random read p95
823.3 µs
905.2 µs
Random write p95
1,221 µ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 Controlled endpoints · one iperf3 stream · 100 Mbit/s rate setting
Metric DigitalOcean s-2vcpu-4gb Vultr vc2-2c-4gb
Download · endpoint 1
100.1 Mbit/s
100.1 Mbit/s
Download · endpoint 2
100.1 Mbit/s
100.1 Mbit/s
Upload · endpoint 1
100.1 Mbit/s
100.1 Mbit/s
Upload · endpoint 2
100.1 Mbit/s
100.1 Mbit/s
Latency · endpoint 1
0.68 ms
2.95 ms
Latency · endpoint 2
3.03 ms
0.42 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 DigitalOcean s-2vcpu-4gb Vultr vc2-2c-4gb
In-memory throughput
1,479 transactions/s
2,073 transactions/s
In-memory average latency
2.70 ms
1.93 ms
Storage-bound throughput
1,246 transactions/s
1,581 transactions/s
Storage-bound average latency
3.21 ms
2.53 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.