Skip to content
fx-blog
Series · 4 parts · 16 min

Load Testing with surge

  1. Part 14 min readBeginnerUp next

    Your Load Test Went Green. What Did It Measure?

    A load test's number is always true about something — and it may be true about your laptop. surge watches its own CPU, marks a run untrustworthy above 85 % instead of reporting a pass, and keeps 512 bytes of what the server replied to every distinct failure.

  2. Part 24 min readIntermediate

    Closed Loops Hide the Cliff. Open Arrivals Find It.

    Against one server frozen three seconds in every ten, 30 concurrent users measured p95 23 ms and 30 arrivals a second measured p95 2,523 ms. The closed loop backs off exactly when the system is in trouble, so its samples come from the windows where nothing was wrong.

  3. Part 34 min readIntermediate

    Write the Storefront Journey, Then Read the Verdict

    A load test with no thresholds has no way to fail, so its green means it finished. Write the thresholds first, then the journey: storefront's run came back FAIL, 2 of 3 breached, 979 of 3,604 requests failed — while p95 passed at 41.5 ms.

  4. Part 44 min readAdvanced

    Several Machines, One p99 You Can Defend

    Three storefront agents reported p99 of 43.52, 42.50 and 42.50 ms. Their average is 42.837; the fleet's p99 is 42.496. surge merges the agents' histograms bucket by bucket and evaluates the thresholds once, so several machines produce one verdict.