Tune rate limits and quotas under realistic load #55

New issue

Open

opened 2026-07-01 00:59:18 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:59:18 +00:00

(Migrated from github.com)

Problem

The initial rate-limit and quota values were placeholders. Before launch they must be validated against realistic traffic so legitimate clients aren't throttled while the origin stays protected on cold paths.

Acceptance criteria

A load scenario exercises hot (cached) and cold (origin) paths.
Rate-limit and quota defaults are adjusted based on the results and documented.
The origin stays within target latency under the modeled peak.
The tuning methodology and chosen values are recorded.

Notes

Most hot traffic should never reach the origin; tune for the cold-path worst case.

## Problem The initial rate-limit and quota values were placeholders. Before launch they must be validated against realistic traffic so legitimate clients aren't throttled while the origin stays protected on cold paths. ## Acceptance criteria - [ ] A load scenario exercises hot (cached) and cold (origin) paths. - [ ] Rate-limit and quota defaults are adjusted based on the results and documented. - [ ] The origin stays within target latency under the modeled peak. - [ ] The tuning methodology and chosen values are recorded. ## Notes Most hot traffic should never reach the origin; tune for the cold-path worst case.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#55

No description provided.

Rows
Columns