Ship & Quality · LOCAL TOOL
Fixed-Window Queue Planner
Calculate dispatch batches for a fixed-window limit using its capacity, usage already consumed, window length, and time remaining until reset.
No API call
Your input
LOCALResult
Run the tool to see a result.
Your result will appear here. Input is not saved.
WHY THIS TOOL EXISTS
A focused job, not a black box.
The first partially used window is handled separately from later full windows. Setting reset to zero explicitly starts a new window, which helps expose boundary assumptions in queue planning.
How to use it
- Choose a fixed-window limit and enter the current usage.
- Enter the remaining reset time and queued request count.
- Read batch counts and dispatch offsets from now.
TRY A WORKING EXAMPLE
Start with known input.
Load this sample into the workspace, run the tool, and compare the result shown below.
Show sample input
{
"requests": "12",
"capacity": "5",
"used": "3",
"window": "1000",
"reset": "400"
}Expected sample result from the local tool
3 batch(es) · last batch at 1400 ms.
{
"model": "fixed window, instantaneous batch dispatch",
"requests": 12,
"batches": [
{
"atMs": 0,
"count": 2
},
{
"atMs": 400,
"count": 5
},
{
"atMs": 1400,
"count": 5
}
]
}A planning model only. Sliding windows, token buckets, concurrency, and actual provider policies can produce different schedules.
LIMITS AND INTERPRETATION
What the result cannot tell you.
Maximum 10000 queued requests. Assumes instantaneous dispatch at explicit fixed-window boundaries. Sliding-window, token-bucket, concurrency, and provider-specific rules are outside the model.
Inputs are processed in this page and are not written to local storage.