THE NUMBERS, EXPLAINED
How to use this calculator.
Traffic rate and error probability stay constant within the entered stage schedule. Stages are sequential; potential failures are expected counts, not forecasts.
Start with your inputs
Enter canary stages (minutes), canary traffic share by stage (%), request arrival rate (requests/minute), canary error scenario (%). Keep amounts in the units shown on each field. The example is a starting point, not a recommended value.
| Input | Example value |
|---|---|
| Canary stages (minutes) | 10,20 |
| Canary traffic share by stage (%) | 10,50 |
| Request arrival rate (requests/minute) | 100 |
| Canary error scenario (%) | 2 |
A worked example
With the example inputs above, canary-exposed requests (count) is 1,100. Change the inputs to explore your own scenario.
| Result | Example answer |
|---|---|
| Canary-exposed requests (count) | 1,100 |
| Expected canary failures (count) | 22 |
How this is calculated
Canary-exposed requests (count)
Multiply each stage duration by traffic share and arrival rate, then add.
Expected canary failures (count)
Multiply exposed requests by the supplied error rate.
Symbols and units
- a
- Canary stages (minutes)
- b
- Canary traffic share by stage (%)
- c
- Request arrival rate (requests/minute)
- d
- Canary error scenario (%)
Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.
Assumptions and limits
Traffic rate and error probability stay constant within the entered stage schedule. Stages are sequential; potential failures are expected counts, not forecasts.
Calculations use the values you enter. Blank or invalid inputs show an error instead of silently substituting zero. Results are displayed to useful precision; calculations retain the underlying numeric precision.
Questions about this tool
What does the result tell me?
Canary-exposed requests (count); Expected canary failures (count). The result applies to the method and inputs described above. Check the units and assumptions before using it in a decision.
Why might another calculator differ?
Differences in units, rounding, timing or model definitions can produce different answers. Compare the input definitions and the method, rather than only the final number. For this tool: Traffic rate and error probability stay constant within the entered stage schedule. Stages are sequential; potential failures are expected counts, not forecasts.
Are my inputs stored or sent to AI?
Calculations on this page happen in your browser. The separate AI question finder sends its submitted conversation to OpenAI; these calculator fields are not sent. Favourites and recent tool names are stored locally. A shared link contains the inputs you choose to include.
Further reading
OpenStax Prealgebra 2e — arithmetic and proportions ↗
Background reading; this does not imply endorsement or independent review of SumFizz.
Review status
Software example and browser checks are recorded in our quality report. No external expert review is claimed. Created with coding assistance; calculations run as ordinary browser code.
Read the quality report →