feat: generated execution SDK#4776
Draft
yaacovCR wants to merge 2 commits into
Draft
Conversation
|
@yaacovCR is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
This was referenced Jun 2, 2026
Open
Rebase on 17.x.x and carry the static document plus raw runtime variable values through compiled validated execution args so root-selection-set tracing has the execution context it needs. Simplify compiled execution entrypoints by sharing validated-argument error handling across execute modes.
Rebase on 17.x.x on top of the compile operations commit and keep generated validated execution args compatible with diagnostics tracing by carrying the static document and raw runtime variable values. Add generated executor kitchen-sink scenarios, a dedicated CI job, and a strict npm run generate:coverage harness for small generated coverage fixtures. Specialize no-variable generated entrypoints and built-in scalar completions so unreachable generated branches do not block complete V8 range coverage of the targeted generated fixture. Simplify generated coverage tests and runner edge-path fixtures by factoring repeated executor setup.
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
1 participant
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.
Depends on:
Add source generation for specialized execution modules.
Benchmarks were run on Node v24.14.1 against 17.x.x, with the compiled executor parent included as an additional comparison.
The generated path shows these rough ops/sec changes compared to regular execution, with percentage comparison to compilation only also included.
We also compared with comparable benchmarks to those used by
graphql-jit.graphql-jitis still faster! The remaining performance gap possibly largely coming from preserving graphql-js 17.x null-prototype semantics for runtime maps including all results objects and all inputs.Below numbers compare the generated SDK performance to regular execute, with percentage comparison to compilation also included.