Request waterfall on load

Pixel 04
HTTP/2HTTP/2Mobile users60 req/sNode API2 vCPU · 2 GBNode API2 vCPU · 2 GBNode API2 vCPU · 2 GBNode API2 vCPU · 2 GBNode API2 vCPU · 2 GBNode API2 vCPU · 2 GBNode API2 vCPU · 2 GB
HTTP/2HTTP/2Mobile use…60 req/sNode APINode APINode APINode APINode APINode APINode API

Fix the board. Turn every goal green.

Traffic
60 req/s · reads only
Limit
Node API answers about 100 req/s
Bill
  • Node API × 756 USD/mo
56 of 70 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.

The home screen call makes the screen API ask six services one after another. p99 is 340 ms and must be under 160 ms. All six services stay and must be reachable. Use at most 8 edits and 70 USD/month.

09:40 UTC. Home screen p99 is 340 ms. The trace shows six calls end to end, each waiting for the one before.

A page waits for its slowest callDrag or use arrow keys to change the calls per page

Calls per page: 20 · 18% of pages wait 2.0 s

Parts you can add: Node API, App backend. At most 8 parts. Budget: 70 USD/mo.

Tap a part to add it, or drag it onto a trace.Click a part to add it, or drag it onto a trace.