Overloaded database

Level 1 of 41
VPS · 2 vCPU · 8 GB16 USD/moSQLUsers2,000 req/sAPI server1 vCPU · 1 GBPostgres0.5 vCPU · 2 GB
VPS16 USD/moHTTP/2SQLUsers2,000 req/sAPI server1 vCPU · 1 GBPostgres0.5 vCPU · 2 GB

Take load off the database.

Traffic
2,000 req/s · 95% reads
Limit
Postgres answers about 1,000 reads/s
Bill
  • VPS 2 vCPU · 8 GB16 USD/mo
16 of 20 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.

Users send 2,000 requests/s. The database answers about 1,000 reads/s, so requests wait and fail. Most requests read the same data. Put a cache between the API and the database.

Parts you can add: Redis cache. At most 1 part. Budget: 20 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.