Performance
Real workloads. Real networks. Honest baselines.
Every benchmark on this page links to its full methodology — workload, network shape, comparison baseline. We publish parity results too, because honesty is the differentiator.
Network shape methodology
Network shape is the dominant variable in distributed-database performance. Every benchmark documents the RTT, bandwidth, and loss profile it ran on. Reproducible harnesses are linked from each result.
- RTT, bandwidth, and loss simulated with deterministic shapers
- WAN reference shape: 50 Mbit, 170 ms RTT, 0.1% loss
- LAN reference shape: 1 Gbit, sub-1 ms RTT, 0% loss
- Each scenario runs against a comparison baseline — never naked numbers
- Source code and raw output published alongside each report
Workload methodology
Application workloads behave differently. We measure three shapes that cover most production traffic — and report them separately so you can pick the one closest to yours.
- Single-row — high-rate small queries with frequent round trips
- Pool-borrow — workloads dominated by connection acquisition and reuse
- Bulk — large transfers (BCP-class loads, COPY, mysqldump-style restores)
- Each workload reports median and high-percentile throughput separately
Headline results
Every row links to a full methodology section.
| Workload | Network shape | Result | Baseline |
|---|---|---|---|
| WAN throughput | 50 Mbit / 170 ms RTT | ~2.5x | Typical proxy baseline |
| Pool-borrow heavy | WAN | ~2.3x | Typical proxy baseline |
| LAN baseline | 1 Gbit / sub-1 ms | Parity | Typical proxy baseline |
| SQL Server bulk (cloud) | Cloud cross-AZ | Up to 139x | Native client tooling |
| MySQL single-row | WAN | Up to 70x | Native client tooling |
Numbers reflect representative results from the harnesses linked above. Your workload, your network, your numbers — see them on a 30-minute demo.
Where DBWarp doesn't win
On low-latency LAN connections, DBWarp runs at parity — there's no penalty for keeping it in the data path, and there's no headline number to claim. We publish parity results because the alternative is dishonest. Performance gains scale with the network challenge: the further the database, the bigger the win.
Want the numbers on your workload?
A 30-minute demo with your real network shape, your real database, your real queries.