Aglet

Verify batch sizes for coverage, runtime, and resource headroom

Verification must show that a selected batch size handles the records it promises without shifting pressure into a shared resource. Run lower, selected, and higher sizes on one fixed ordered input. Compare item identities and durable outputs alongside memory, query, and queue behavior.

Check whether the outcome improved

  1. Verify lower and selected sizes

    Run the fixed input at the lower control and proposed size. Confirm every expected identity appears once, outputs and terminal states match, and checkpoint or resume behavior is coherent. Record query and resource readings for both rather than trusting total duration.

  2. Verify the higher boundary

    Exercise the larger size that previously showed pressure or coverage drift. Confirm the guard rejects, limits, or handles it according to policy, and that no partial batch is labeled complete. Inspect connection, lock, memory, and queue effects after workers settle.

  3. Verify changed ordering resistance

    Repeat with an equivalent input order or resumed checkpoint if the contract permits. Check that selection and commit boundaries remain stable and no item is lost when a batch ends at a cursor boundary. Reconcile all outputs against the independent expected set.

What to carry forward

Accept when lower, selected, and higher sizes have exact coverage, documented checkpoint behavior, and resource readings within the chosen guard. Keep the tested input range visible. Reopen verification if larger batches silently omit or repeat records, or if the guard harms neighboring work.

Technical background: Rails guides.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow