Write down the traffic mix before comparing quote timings
The last benchmark sent one route repeatedly. Dispatch says the slow period contains mostly unique routes and a small number of expensive multi-stop quotes.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Workload modeling · Reproducibility
Estimated field mix
- Performance engineering70%
- Quality engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional freight broker sees slow quote responses at dispatch handover. The service looks healthy in average-latency charts, yet a few long requests occupy every worker. Build a small synthetic quote service and controlled dependency stub before taking implementation tickets.
Setup prerequisites
- Create a local quote endpoint and a deterministic carrier-price stub; no repository or dataset is supplied.
- Use synthetic routes and a fixed workload manifest. Record runtime, machine resources and instrumentation settings.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Create a seeded mix of 70% single-stop, 25% multi-stop and 5% invalid requests across 1,000 synthetic routes.
- Record concurrency, arrival rate, seed, payload sizes, runtime and resource limits in the run manifest.
- Count every attempted request, including validation failures and client timeouts, against the expected result class.
Implementation constraints
- Keep the fixture bounded; random seeds must reproduce both request order and expected quote inputs.
Verification to include
- Replay the same seed twice and compare request identities and expected outputs.
- Change the seed and confirm the traffic proportions stay within the declared rounding rule.
Deliverables
- Workload manifest and deterministic request generator
Rollout and recovery
Commit the baseline manifest separately; a workload change starts a new comparison series.
Value of the work
For the engineer: Learn to distinguish queueing, dependency delay, CPU work and measurement mistakes using reproducible observations.
For the team: Produce a reviewable diagnosis and guarded changes that could guide a team investigating customer-visible latency.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.