Tinker Load balancing

by Samy (Kondasamy Jayaraman) · drawn with Colorfigures by April Zhu

p50 54 ms, p99 1,000 ms, over 395 requests.

Cedar dies and Dogwood turns slow but answering. 149 failed, 0% extra copies.Ash 0 waiting · Birch 0 waiting · Cedar 0 waiting · Dogwood 0 waiting

Chapter 7 of 7

Route the sale

Sale day again: Cedar will die and Dogwood will turn slow but answering. Carts now live in a shared store.

This chapter: Which rule, health check and hedge keep the slowest customers fastest?

About this chapter

You will learn

  • How rules, health checks and hedging work together
  • Reading p99 against a budget for extra copies
  • Why more than one setup can be best

Words you’ll meet

Budget
Limits the team sets: here, no failed requests and a cap on extra copies.

Step 1 of 2

The team’s : no failed requests, and hedging may add at most 15% extra copies.

Find the lowest p99 within it.

1,000 ms p99 OVER BUDGET

Rule
The sale against the team’s budget
MeasureThis setupBudget
Failed requests1490
Extra copies0%at most 15%
p991,000 mslowest wins

Carts live in a shared store now, so sticky sessions stay off.

A simulated sale: Larkspur’s own traffic and planning numbers, not a measurement of any real server or balancer.