Loss across the ocean

Wire 21
HTTP/2Partner apps100 req/sAPI server2 vCPU · 1 GB
HTTP/2Partner apps100 req/sAPI server2 vCPU · 1 GB

Fix the board. Turn every goal green.

Traffic
100 req/s · reads only
Limit
API server answers about 6,700 req/s
Bill
  • API server8 USD/mo
8 of 100 USD/mo

Goals

Not tested yet

99 of 100 requests finish faster than this.The share of requests that fail or get no answer.What the servers and services cost each month.

A cross-ocean path has 140 ms RTT and 1 percent loss. One TCP connection must carry 100 objects/s at 50 KB each. Keep p99 below 500 ms and errors below 1 percent.

0:00. Transfers across the ocean stall. Graph: delivered objects stay below demand while p99 passes 500 ms.

Connections and streamsDrag or use arrow keys to change the protocol

HTTP/1.1 · connections: 6 · 30 files in 7 round trips, 630 ms