Reviewed measurements

Compare the evidence.

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

Selected plans
DigitalOceans-2vcpu-4gb
Vultrvc2-2c-4gb
Matching observed resources: x86_64 · 2 vCPU · 3.8 GiB RAMSource location: Bangalore, IN · same agent build and methodology.
CPU allocation
2 vCPU
2 vCPU
Observed memory
3.8 GiB
3.8 GiB
Processor
DO-Regular
Intel Xeon (Cascadelake)
Location
Bangalore, INblr1
Bangalore, INBLR
List price
$24.00 / month$0.0357 / hour · before tax
$20.00 / month$0.027 / hour · before tax
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
Each column is one deployment. Matching context does not establish equivalent physical hosts.Benchmark medians · network trials linked separately
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

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Single thread
361.4events/s72% of 500
463.6events/s93% of 500
All 2 vCPUs
674.0events/s67% of 1,000
915.0events/s92% of 1,000
gzip compression
180.5MiB/s72% 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

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Read
6,067MiB/s76% of 8,000
7,836MiB/s98% of 8,000
Write
6,004MiB/s75% of 8,000
7,607MiB/s95% of 8,000

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

PerformanceReviewed data
DigitalOceanBangalore, IN
VultrBangalore, IN
03 /

Disk performance

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

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Sequential read
5,471MB/s
3,465MB/s
Sequential write
1,860MB/s
2,989MB/s
Random read
83,421IOPS
152,482IOPS
Random write
61,369IOPS
169,197IOPS
Random read p95
561.2µs
325.6µs
Random write p95
823.3µs
305.2µ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

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
Frankfurt · source
Network reportSeparate VM test · 17 Oct 2026, 17:32 UTCBangalore, IN · Frankfurt, Germany (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 17:03 UTCBangalore, IN · Frankfurt, Germany (Clouvider)
Frankfurt · Download
420.4Mbit/s
238.4Mbit/s
Frankfurt · Upload
158.2Mbit/s
78.3Mbit/s
Frankfurt · HTTP latency
131.4ms
190.7ms
Frankfurt · HTTP jitter
0.24ms
0.28ms
New York · source
Network reportSeparate VM test · 17 Oct 2026, 17:32 UTCBangalore, IN · New York, United States (2) (Clouvider)
Network reportSeparate VM test · 17 Oct 2026, 17:03 UTCBangalore, IN · New York, United States (2) (Clouvider)
New York · Download
302.2Mbit/s
140.3Mbit/s
New York · Upload
91.0Mbit/s
39.6Mbit/s
New York · HTTP latency
201.9ms
315.9ms
New York · HTTP jitter
0.05ms
0.31ms

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
DigitalOcean2 vCPU · 3.8 GiB
Vultr2 vCPU · 3.8 GiB
05 /

PostgreSQL performance

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

MetricDigitalOcean s-2vcpu-4gbVultr vc2-2c-4gb
In-memory throughput
1,898transactions/s
4,049transactions/s
In-memory average latency
2.10ms
0.99ms
Storage-bound throughput
1,296transactions/s
3,230transactions/s
Storage-bound average latency
3.08ms
1.24ms

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.

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