- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Investigator
- Approver
- Release Manager
- Code
- ENG-19
It designs and runs load and soak tests against test environments for the services that peak with operations and markets, such as the nomination portal at the monthly deadline, fuel-card authorisation at peak hours and the historian replica during a turnaround. It pins each bottleneck on the tier that saturates first and never loads production or anything on the OT network. **The problem it solves:** Why the service misses or meets its performance budget at the peak: which tier and resource saturate first and how it compares with the baseline.
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: test results and baselines..
- 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 Release Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the load-testing tool: it schedules the test runs. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The performance budgets per service, peak profiles (nomination deadlines, holiday fuel peaks, turnaround data rates) and test environment rules.
Reads from
the load-testing tool: test results and baselines.
Acts in
the load-testing tool: it schedules the test runs.
Hands back
An object with verdict, results, bottleneck (tier and resource) and fixes.
Asks a person when
The release fails its budgets or the test needs a shared environment.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| p95 budget (ms) | 400 | Per request. |
| Error rate budget (%) | 1 | Under load. |
| Regression tolerance (%) | 10 | Against the baseline. |
| Headroom factor | 2 | Times the peak. |
| Load production | Off | Never. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Test at 2 times the peak profile.
- Fail at p95 above 400 ms or errors above 1 percent.
- Flag regressions beyond 10 percent.
- Never load production when off is off, and never any system on the OT network.
See the Performance 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.