capacity-estimation
Capacity estimation with numbers computed in code, not in prose. It starts from measured metrics when the system exists, or from order-of-magnitude scenarios and decision thresholds when there are no metrics (exploratory design, PoC), leaning on the business archetype. Covers QPS, storage, bandwidth, Little's law, utilization and queues, fan-out and tail latency, composed availability, shards, backlog and burn rate. Use it when a decision depends on scale ("will it hold?", "how many instances?", "do we need to shard?", "capacity planning", "back-of-the-envelope").
- License
- MIT
Pinned to revision a2c346f89684, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/capacity-estimation/SKILL.md
- skills/capacity-estimation/references/measurement.md
- skills/capacity-estimation/references/numbers.md
- skills/capacity-estimation/scripts/capacity.py
- skills/capacity-estimation/scripts/test_capacity.py
Every link opens the file at its source, pinned to the revision this page describes.