Vultr
Shared CPU · 4 GB
The complete benchmark report. Every workload, in one place.
All values below are illustrative sample data. No tests have been run.
CPU performance
sysbench prime workload · same test build.
Single thread
All 2 vCPUs
- 1 thread1,520
- 2 threads2,920
Thread count and test settings stay fixed across comparable instances.
Memory bandwidth
2 GiB working set · sequential operations.
- Read16.4
- Write13.9
- Copy12.2
Disk performance
fio · direct I/O · sequential 1 MiB / QD8 · random 4 KiB / QD32.
| Workload | Throughput | p95 latency |
|---|---|---|
| Sequential read | 2,610 MB/s | 5.0 ms |
| Sequential write | 1,940 MB/s | 6.2 ms |
| Random read | 69,000 IOPS | 0.92 ms |
| Random write | 40,900 IOPS | 1.54 ms |
| Random 70/30 mix | 51,300 IOPS | 1.30 ms |
Read, write, and mixed workloads are represented separately. All values are synthetic.
Network performance
Source: Frankfurt, DE · controlled destination endpoints.
| Destination | Download | Upload | RTT | Jitter | Loss |
|---|---|---|---|---|---|
| Frankfurt | 2.2 Gbit/s | 1.9 Gbit/s | 5.2 ms | 0.3 ms | 0.0% |
| Amsterdam | 1.9 Gbit/s | 1.7 Gbit/s | 10.8 ms | 0.5 ms | 0.0% |
| London | 1.7 Gbit/s | 1.5 Gbit/s | 18.6 ms | 0.7 ms | 0.0% |
Results describe these example paths, not every possible destination.
PostgreSQL performance
PostgreSQL 16 · pgbench read/write · 32 clients · durability enabled.
| Dataset profile | Transactions / sec | p95 latency | Errors |
|---|---|---|---|
| In memory | 3,980 | 10.2 ms | 0 |
| Storage-bound | 1,350 | 30.1 ms | 0 |
Example configuration: 5-minute warm-up · 60-second measured runs.
Consistency across instances
PostgreSQL in-memory workload · three sample instances.
| Instance | CPU 1 thread | Memory read | Random read | PostgreSQL |
|---|---|---|---|---|
| A | 1,540 events/s | 16.8 GB/s | 70,500 IOPS | 4,150 tx/s |
| B | 1,520 events/s | 16.4 GB/s | 69,000 IOPS | 3,980 tx/s |
| C | 1,490 events/s | 16.0 GB/s | 67,200 IOPS | 3,860 tx/s |
Inspect the evidence.
Illustrative configuration, sample results, and a clearly labelled demonstration log.
Three instances describe this sample, not every server a provider operates.
A 24-hour test does not establish long-term reliability. Sample downloads contain synthetic values only.