Optimize JavaScript sandbox command startup - #74
Merged
Conversation
This was referenced Jul 22, 2026
luke-lombardi
marked this pull request as ready for review
July 22, 2026 15:18
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.
Summary
@beamcloud/[email protected]Why
The ComputeSDK JavaScript benchmark runs a very short command. The SDK was paying separate status, stdout, and stderr requests plus a 100 ms polling interval after the command had already finished. Concurrent first-use calls could also duplicate runtime preparation.
Exact-artifact verification
794837a@beamcloud/[email protected]61bb4727, plus computesdk/computesdk#659 at19905c7df11dd7efA fresh benchmark clone installed the ComputeSDK adapter branch as a packed package and resolved Beam JS 1.0.13 from the public npm registry. The only benchmark-source adjustment supplied the target gateway URL. All official modes completed without SDK errors in staging:
The staging benchmark workspace was temporarily given the official 100-sandbox quota for the burst gate and restored afterward.
Validation
npm cinpm test -- --runInBand— 138/138 tests passednpm run build— ESM and CJS builds passedRelease
Published as
@beamcloud/[email protected]from the canonicalbeam-client/jspackage.