Publish the worker-pool contract and benchmark limits
A build tool and a request server both plan to reuse the pool despite different fairness, blocking, and shutdown requirements.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Benchmarking · Documentation · Capacity planning
Estimated field mix
- Systems programming70%
- Developer tooling30%
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 image-indexing utility runs CPU-only synthetic jobs through a Rust worker pool. Its prototype loses wakeups, blocks shutdown, and treats cancellation as completion. Build a local library and deterministic concurrency harness; image content, GPU work, and production deployment are excluded.
Setup prerequisites
- Mutexes and condition variables
- Atomics
- Thread lifecycle
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- SCONCUR-102 · Reject work when the bounded queue is full
- SCONCUR-101 · Define queue ownership before starting worker threads
- SCONCUR-103 · Close the lost-wakeup gap between predicate and sleep
- SCONCUR-104 · Keep cancellation distinct from successful completion
- SCONCUR-105 · Prevent priority work from starving maintenance forever
- SCONCUR-106 · Remove a lock-order inversion in completion reporting
- SCONCUR-108 · Drain accepted jobs without hanging process shutdown
- SCONCUR-109 · Capture a concurrency failure without megabytes of logs
Acceptance criteria
- Document supported job behavior and prohibited blocking assumptions
- Report throughput, queue wait, memory, and shutdown duration for declared workloads
- List cases where a runtime-native executor is preferable
Implementation constraints
- Do not generalize results beyond the recorded machine and workload profiles.
Verification to include
- Reproduce one CPU-bound and one mixed-duration benchmark from a clean checkout.
- Run the unsupported permanently blocking job and confirm the guide predicts the outcome.
Deliverables
- Contract, benchmark manifest, and adoption checklist
Rollout and recovery
Require each adopter to select and verify a workload profile.
Value of the work
For the engineer: Practice happens-before reasoning, ownership transfer, cancellation and liveness testing.
For the team: Review a worker primitive whose overload and shutdown behavior are predictable before it supports build or media workloads.
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.