Skip to content

Re-tune queue concurrency for multi-customer volume #4892

Description

@JSONbored

Problem: Queue batch size and concurrency are hardcoded and explicitly sized (per an in-code comment) around today's small, known set of repos and their shared GitHub rate-limit bucket — not a multi-customer volume model.

Area: ORB / Cloud

Proposal: Make these settings configurable and re-derive sane defaults for a plausible multi-tenant volume, informed by the scaling work elsewhere in this milestone.

Deliverables:

  • Configurable, better-justified queue tuning, documented with the reasoning behind the new defaults.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions