The cache key

Cache 09
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 7,500 reads/s
Bill
  • Redis cache4 USD/mo
  • Postgres4 USD/mo
8 of 30 USD/mo

Goals

Not tested yet

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

Tracking parameters create 100 raw keys for each product. The small cache hits only about 3 percent of raw keys. Reach a 90 percent hit ratio and keep p99 below 150 ms. Do not change the requests.

0:00. The cache hit ratio is near 3 percent. Graph: database reads track total reads almost exactly.

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.