Problem: The job queue's batch size, concurrency, retry count, and retry delay are all sized around today's low, known volume — not a multi-tenant model. (This is the queue-specific half of the multi-tenancy category's broader queue-tuning item — tracked separately here because the two categories care about different aspects: isolation there, raw throughput here.)
Area: ORB / Scaling
Proposal: Re-derive queue tuning from realistic multi-tenant volume projections, informed by load-testing once it exists (see below).
Deliverables:
- Documented, re-justified queue configuration for multi-tenant volume.
AMS Cloud Readiness cross-reference (added 2026-07-12)
See also #5223 in the new AMS Cloud Readiness milestone (#28) — the AMS-side parallel to this exact problem, already citing this issue as precedent. Keep both sides in sync if either design changes.
Problem: The job queue's batch size, concurrency, retry count, and retry delay are all sized around today's low, known volume — not a multi-tenant model. (This is the queue-specific half of the multi-tenancy category's broader queue-tuning item — tracked separately here because the two categories care about different aspects: isolation there, raw throughput here.)
Area: ORB / Scaling
Proposal: Re-derive queue tuning from realistic multi-tenant volume projections, informed by load-testing once it exists (see below).
Deliverables:
AMS Cloud Readiness cross-reference (added 2026-07-12)
See also #5223 in the new AMS Cloud Readiness milestone (#28) — the AMS-side parallel to this exact problem, already citing this issue as precedent. Keep both sides in sync if either design changes.