Skip to content

fix(compose): expose the worker concurrency limit - #1110

Open
wcy12378 wants to merge 1 commit into
Tencent:mainfrom
wcy12378:codex/compose-worker-concurrency
Open

wcy12378 wants to merge 1 commit into
Tencent:mainfrom
wcy12378:codex/compose-worker-concurrency

Conversation

@wcy12378

Copy link
Copy Markdown

Related to #951, addressing its optional Compose concurrency setting. Execution-slot wait telemetry remains in #956; project admission and fairness scheduling are outside this change.

The platform binary already accepts -worker-concurrency, but Compose only passes the workspace path. Operators therefore have to replace the whole service command to tune sandbox execution slots.

Pass ${AGENTFLOW_WORKER_CONCURRENCY:-8} as the existing flag's value, add the setting to .env.example, and document its scope and how to apply it. The default remains 8, including installations whose existing .env has no new setting. The exec-form command preserves the workspace argument and passes the limit as one argument.

Validation:

  • Docker Compose 5.1.3: docker compose --env-file .env.example --profile platform config --format json rendered the expected complete platform argv for unset, empty, 3, and 12 environment overrides.
  • A separate copy of .env.example with the new setting omitted also rendered -worker-concurrency 8, verifying existing installation compatibility.
  • Inspected cmd/agentflow/main.go and internal/runtime/sandbox_manager.go: the flag defaults to 8 and supplies the manager's shared execution-slot channel.
  • py -X utf8 scripts/check-public.py and git diff --check passed.

No services were started or recreated. Go tests, a live multi-run workload, and browser acceptance were not run; this change only wires the existing flag into Compose and documents it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant