capacity-estimation

Calculate QPS, storage, bandwidth, and cache sizing for system design.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill capacity-estimation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capacity-estimation
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-system-design/skills/capacity-estimation
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill capacity-estimation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you translate vague system requirements into concrete, quantifiable infrastructure needs, preventing costly over-provisioning or under-provisioning.

Core Features & Use Cases

  • Traffic Calculation: Estimates QPS (Queries Per Second) for reads and writes based on user activity and ratios.
  • Storage Sizing: Calculates required storage for data over specified retention periods, differentiating between hot, warm, and cold tiers.
  • Bandwidth Estimation: Determines inbound and outbound bandwidth needs, factoring in CDN usage.
  • Cache Sizing: Helps determine appropriate cache sizes based on the working set principle.
  • Database Connection Planning: Assesses database connection pool requirements and potential bottlenecks.
  • Use Case: When designing a new social media platform, use this Skill to estimate the QPS, storage, and bandwidth needed for 1 million daily active users over three years.

Quick Start

Use the capacity-estimation skill to estimate the infrastructure needs for a photo-sharing app with 50 million daily active users.

Frequently Asked Questions about capacity-estimation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate infrastructure capacity for a system design with a million daily active users?

To estimate infrastructure capacity, calculate QPS based on user activity and read-to-write ratios, then project storage, bandwidth, and cache sizing over your data retention period. This quantifies requirements to prevent over-provisioning or under-provisioning.

What is the best way to calculate QPS and storage sizing for a new application?

The best way to calculate QPS and storage sizing is to apply back-of-envelope estimation using daily active users, read-to-write ratios, and object sizes. This determines traffic load and differentiates storage across hot, warm, and cold tiers.

How does bandwidth estimation factor in CDN usage for high-traffic systems?

Bandwidth estimation factors in CDN usage by calculating inbound and outbound bandwidth needs based on QPS and object sizes. This determines network throughput requirements and identifies potential infrastructure bottlenecks during traffic spikes.

Can I use back-of-envelope estimation for database connection pool planning?

Yes, you can use back-of-envelope estimation for database connection pool planning. It assesses connection pool requirements by analyzing estimated QPS, helping identify potential database bottlenecks before infrastructure deployment.

When do I need to calculate cache sizing using the working set principle?

You need to calculate cache sizing using the working set principle when designing systems requiring low latency. It determines appropriate cache sizes based on active user data, ensuring frequently accessed objects remain in memory.

Does capacity planning differentiate storage requirements across data retention tiers?

Yes, capacity planning differentiates storage requirements by calculating needed capacity over specified retention periods. It separates storage into hot, warm, and cold tiers to optimize infrastructure costs and data access speeds.