Missing keys

Cache 13
HTTP/2SQLUsers5,000 req/sRedis cache0.25 vCPU · 0.5 GBPostgres0.5 vCPU · 1 GB
HTTP/2SQLUsers5,000 req/sRedis cache0.25 vCPU · 0.5 GBPostgres0.5 vCPU · 1 GB

Fix the board. Turn every goal green.

Traffic
5,000 req/s · reads only
Limit
Postgres answers about 500 reads/s
Bill
  • Redis cache4 USD/mo
  • Postgres4 USD/mo
8 of 30 USD/mo

Goals

Not tested yet

99 of 100 requests finish faster than this.How busy the busiest CPU is. Keep room for spikes.What the servers and services cost each month.

Of all lookups, 99 percent ask for IDs that do not exist. Normal cache entries do not stop these reads from reaching the source. Keep source CPU below 70 percent and p99 below 150 ms.

0:00. Source CPU is far above 70 percent. Graph: cache misses are almost equal to total lookups.

Parts you can add: Redis cache. At most 16 parts. Budget: 30 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.