TTL and stale reads

Level 9 of 41
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

Tune the parts. Turn every goal green.

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

Goals

Not tested yet

Reads that returned old data.The share of reads the cache answers.99 of 100 requests finish faster than this.What the servers and services cost each month.

Each second, 4,995 reads and 5 writes reach 1,000 keys. Tune the TTL. Fewer than 1 percent of the 299,700 reads may be stale. More than 80 percent must hit the cache.