Configure Playground runtime request workers - #2088
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2087.
What changed
runtime.workerssupport for integers from 1 through 64 orauto.Why
Playground applies mounted resources to every request worker. Large generated runtimes can therefore multiply startup work by six even when the workload needs only one request worker. Bounded execution concurrency remains an independent orchestration concern.
Verification
npm run buildnpm run test:runtime-workersnpm run test:runtime-neutral-contractsnpm run test:recipe-runtime-backend-normalizationnpm exec -- tsx tests/playground-cli-runner-bootstrap-ini.test.tsgit diff --checkThe combined
test:runtime-servicescommand reaches an existing macOS native-MariaDB containment failure after its generic and external-MySQL portions pass; this change does not touch that provider.AI assistance
OpenCode using
openai/gpt-5.6-solimplemented the runtime worker-count contract and tests after diagnosing the large-mount startup scaling failure. Chris Huber reviewed and owns the submitted change.