Load run #2 finished
All load runsDEMO-018 · 6 simultaneous browser(s) · window 1m 30s · ramped over 15s · target v1.1.0
Passes completed
130
130 passed · 0 failed
Error rate
0%
under load
Throughput
84.6
passes per minute
Median (p50)
3.301s
alone it took 1.924s
p95
3.899s
1 in 20 was slower than this
Slowdown
1.72×
median vs on its own
What this says
On its own this test takes 1.924s. With 6 running at once the median became 3.301s — 1.72× slower — and the slowest 5% took over 3.899s.
It managed 130 passes against a projection of 276. A real count well under the projection means the application slowed down — which is the finding, not a problem with the plan.
Response time over the run flat = shrugged it off; climbing = you found the limit, and where
Which step got slow the question a request-per-second number cannot answer
| Step | Samples | Average | p95 | Worst |
|---|---|---|---|---|
| track a shipment in transit | 130 | 0.51s | 0.653s | 0.781s |
| track a delivered shipment | 130 | 0.385s | 0.52s | 0.634s |
| track an unknown number | 130 | 0.375s | 0.494s | 0.547s |
| goto http://127.0.0.1:8000/demo/freight/ | 130 | 0.297s | 0.425s | 0.498s |
| open the home page | 130 | 0.297s | 0.425s | 0.498s |
| click #track-btn | 390 | 0.194s | 0.304s | 0.388s |
| fill #track-id | 390 | 0.078s | 0.151s | 0.219s |
| wait_for_selector #track-result, #track-not-found | 390 | 0.08s | 0.146s | 0.214s |
| goto http://127.0.0.1:8000/demo/freight/track/ | 390 | 0.071s | 0.125s | 0.199s |
| inner_text #track-status | 130 | 0.025s | 0.052s | 0.075s |
Sorted by p95 — the top row is where the application hurts most under load.