Sticky trouble

Scale 05
HTTP/2HTTP/2HTTP/2HTTP/2Users2,400 req/sLoad balanc…1 vCPU · 1 GBNode API1.5 vCPU · 1.5 GBNode API1.5 vCPU · 1.5 GBNode API1.5 vCPU · 1.5 GB
HTTP/2HTTP/2HTTP/2HTTP/2UsersLoad bala…Node APINode APINode API

Fix the board. Turn every goal green.

Traffic
2,400 req/s · 95% reads
Limit
Node API answers about 1,500 req/s
Bill
  • Load balancer (L7)4 USD/mo
  • Node API × 318 USD/mo
22 of 22 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.

Each deploy restarts the 3 API nodes one at a time, for 10 s each. Since then, p99 reaches 6 s and 9 percent of page views fail, while one node idles. 2,400 views/s, 90 percent in signed-in sessions. Bring p99 under 150 ms and errors under 2 percent. Max 4 edits, no new spend.

1:05. Rolling deploy in progress. p99 is 7 s. Graph: CPU by API node: api-c 100 percent, api-a 43 percent, api-b 6 percent.