Model the System Before Building It
Find the worst queue during the upload burst
Start quietly before a late burst
Even a service with enough average capacity can accumulate unfinished image requests during a burst or worker outage.
BOTIE
The inputs we are comparing
Requests arriving per interval
Short burst
- 02
- 17
- 21
Quiet start cannot store capacity
- 00
- 18
Requests that can finish per interval
Short burst
- 04
- 14
- 24
Quiet start cannot store capacity
- 05
- 13
Result for short burst
3
A temporary stoppage leaves work for later
This check uses the pieces from “Retain unfinished requests across intervals”.
BOTIE
- Requests arriving per interval
- 03
- 14
- 24
- 30
- Requests that can finish per interval
- 05
- 10
- 23
- 38
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
Why could a trace finish empty while still exceeding the available queue space earlier?
Keep the full workload trace and its maximum; final backlog and average rate cannot certify burst handling.
This counts fixed-size requests in discrete intervals. It does not measure individual latency or implement queue limits and retries.
Work through the Python challenges →