Knowledge Guide
HomeSystem DesignCapacity Estimation

easy Drill: daily & peak QPS for a social feed

Drill

A social app has 20M daily active users, each opening their feed 10 times/day. Estimate the average and peak read QPS. Try it before opening the solution.

Anchors: 86,400 ≈ 10⁵ s/day; peak factor ~2–3×.

✅ Worked solution & bounds check

Worked solution

  • Requests/day = 20M × 10 = 2 × 10⁸.
  • Average QPS = 2 × 10⁸ ÷ 10⁵ = ~2,000 QPS.
  • Peak ×3 ≈ ~6,000 QPS.

Bounds: low (peak ×2) ≈ 4K; high (×5, bursty) ≈ 10K. Ratio 2.5× — tight, trustworthy.

Gate: ~6K read QPS is comfortably served by a few cached app servers; no exotic architecture needed yet.

🤖 Don't fully get this? Learn it with Claude

Stuck on Drill: daily & peak QPS for a social feed? Open Claude, copy a block below, and it'll teach you this exact concept — visually and interactively.

🪜 Hint ladder (no spoilers)

Progressively stronger hints — you still solve it.

I'm working on the problem **Drill: daily & peak QPS for a social feed** (System Design). Give me a HINT LADDER: start with the tiniest nudge, then wait. Only reveal the next, stronger hint when I ask. Do NOT show the full solution unless I type 'show solution'. Keep me doing the thinking. If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.
🎨 Explain the approach visually

See the technique, not just code.

Explain the optimal approach to **Drill: daily & peak QPS for a social feed** with a VISUAL walkthrough: trace it on a small concrete example using ASCII art / a step-by-step diagram, narrate what changes each step, then give time & space complexity with a one-line derivation. If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.
🔍 Review my solution

Catch bugs, edge cases, sub-optimality.

I'll paste my solution to **Drill: daily & peak QPS for a social feed**. Review it for correctness, missed edge cases, and time/space complexity, then coach me toward the optimal — don't just rewrite it. Ask me to paste my code now. If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.
🔁 Drill the pattern

Lock in recognition with look-alikes.

Give me 2 problems that use the SAME underlying pattern as **Drill: daily & peak QPS for a social feed**. For each, let me attempt first, then review my answer and name the trigger signal that reveals the pattern. If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.

📝 My notes