THE NUMBERS, EXPLAINED
How to use this calculator.
Packs consecutive records without reordering using the next-fit rule. Each record size must include its serialization separators; the envelope is added once per request. This feasible packing is not an optimal reordering solver.
Start with your inputs
Enter serialized bytes per record in order, maximum records per request, maximum request bytes, fixed envelope bytes per request. Keep amounts in the units shown on each field. The example is a starting point, not a recommended value.
| Input | Example value |
|---|---|
| Serialized bytes per record in order | 200,200,400,100 |
| Maximum records per request | 2 |
| Maximum request bytes | 600 |
| Fixed envelope bytes per request | 50 |
A worked example
With the example inputs above, request count is 2. Change the inputs to explore your own scenario.
| Result | Example answer |
|---|---|
| Request count | 2 |
| Inclusive record ranges | 1–2, 3–4 |
| Request sizes (bytes) | 450, 550 |
How this is calculated
Request count
Scan records in order, starting a new request when adding a record would exceed either cap.
Inclusive record ranges
Report the first and last 1-based record index in each request.
Request sizes (bytes)
Envelope bytes plus all serialized record bytes in each request.
Symbols and units
- a
- Serialized bytes per record in order
- b
- Maximum records per request
- c
- Maximum request bytes
- d
- Fixed envelope bytes per request
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
Packs consecutive records without reordering using the next-fit rule. Each record size must include its serialization separators; the envelope is added once per request. This feasible packing is not an optimal reordering solver.
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?
Request count; Inclusive record ranges; Request sizes (bytes). 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: Packs consecutive records without reordering using the next-fit rule. Each record size must include its serialization separators; the envelope is added once per request. This feasible packing is not an optimal reordering solver.
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: percentages 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 →