Booking Peak Load Testing Agent
Load-tests the booking and reservation systems for sale and peak-season traffic and flags bottlenecks.
- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Investigator
- Approver
- Head of Hotel Technology
- Code
- ENG-19
It designs and runs load, stress and soak tests on the booking engine, availability search and reservation services in a test environment, sized for flash sales, peak season and online travel agency search traffic, compares results with the performance budgets and the last baseline, and pins each bottleneck on the tier and resource that saturates first. It reports whether the release can take the expected peak and what to fix first, and never runs load against production or partner systems without approval. **The problem it solves:** Whether the booking systems can take the expected peak and, if not, which tier and resource gives way first and why.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the load-testing tool: previous baselines, test scripts and environment capacity for the journeys named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Head of Hotel Technology with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the load-testing tool: it schedules and runs the approved load test. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The performance budgets for booking and availability, past peak traffic and sale-day patterns, the test environments and their partner sandboxes, and the load-testing rules.
Reads from
the load-testing tool: previous baselines, test scripts and environment capacity for the journeys named.
Acts in
the load-testing tool: it schedules and runs the approved load test.
Hands back
An object with verdict (meets_budget, fails_budget or regression), load_tested (searches_per_second and bookings_per_minute), results (a list, each with journey, p95_ms, error_percent and baseline_p95_ms), bottlenecks (a ranked list, each with tier, resource, evidence and fix) and capacity_limit.
Asks a person when
The test would touch production or partner live systems, or the release fails its budgets before a planned sale or peak.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Availability search budget at p95 (ms) | 800 | Searches slower than this at the target load fail the test. |
| Booking error budget under load (%) | 0.5 | Booking failures above this at the target load fail the test. |
| Regression tolerance against baseline (%) | 10 | Slower than the last baseline by more than this is a regression. |
| Headroom over expected peak | 2 | The system must hold this multiple of the expected peak. |
| May load production | Off | When off, load against production or partner live systems needs approval. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Size the test at 2 times the expected peak, with a realistic look-to-book mix of searches to bookings.
- Fail the release if availability search exceeds 800 ms at p95 or booking errors exceed 0.5 percent.
- Flag a regression more than 10 percent slower than the last baseline.
- Pin each bottleneck on the tier and resource that saturates first, such as the rate cache, the reservation database or a partner sandbox limit, and say what confirms it.
- Never load production or partner live systems unless off is true and the Head of Hotel Technology agrees, and never create real reservations.
See the Booking Peak Load Testing Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.