Load run #1 finished
All load runsDEMO-018 · 6 simultaneous browser(s) · window 1m 30s · ramped over 15s · target v1.0.0
Passes completed
129
129 passed · 0 failed
Error rate
0%
under load
Throughput
83.3
passes per minute
Median (p50)
3.416s
alone it took 1.924s
p95
3.772s
1 in 20 was slower than this
Slowdown
1.78×
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.416s — 1.78× slower — and the slowest 5% took over 3.772s.
It managed 129 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 | 129 | 0.611s | 0.749s | 0.864s |
| track a delivered shipment | 129 | 0.501s | 0.632s | 0.665s |
| track an unknown number | 129 | 0.473s | 0.608s | 0.725s |
| click #track-btn | 387 | 0.325s | 0.43s | 0.545s |
| goto http://127.0.0.1:8000/demo/freight/ | 129 | 0.27s | 0.395s | 0.457s |
| open the home page | 129 | 0.27s | 0.395s | 0.457s |
| fill #track-id | 387 | 0.069s | 0.145s | 0.21s |
| wait_for_selector #track-result, #track-not-found | 387 | 0.069s | 0.123s | 0.205s |
| goto http://127.0.0.1:8000/demo/freight/track/ | 387 | 0.065s | 0.116s | 0.197s |
| inner_text #track-status | 129 | 0.022s | 0.041s | 0.064s |
Sorted by p95 — the top row is where the application hurts most under load.