A larger screen, mouse and keyboard make designing and running simulations much easier. Open this page on your laptop or desktop to continue.
Step 1 / 2 · Observe
The chapter's example: 300 million monthly active users, 50% of them active each day, 2 tweets per user a day. That is 150 million × 2 ÷ 24 hours ÷ 3,600 seconds ≈ 3,500 tweets a second. In this simulator one CPU core serves about 9,000 requests a second, so one server with half a core (about 4,500) covers the average. The run's peak, from 4 s to 6 s, is twice the average.
Predict: what happens when 7,000 requests a second reach a server that serves 4,500?
Checking saved progress…
Run to measure latency, availability and database pressure.