Pre-warm the app plane on requests that do not need it - #2072
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | b3c9633 | Commit Preview URL Branch Preview URL |
Sep 19 2026, 04:05 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | b3c9633 | Sep 19 2026, 04:07 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
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.
Cold app-plane dispatches are the largest share of dashboard latency: 30% of
/api/*requests land on an isolate that has not evaluated the app graph and pay ~2 s (p50) against ~100 ms warm. Only 43% of those isolates are under 5 s old. The rest have been alive serving/mcp, discovery documents, or proxies, none of which enter the app graph.This change starts the app-plane import in the background (
ctx.waitUntil) on any request that does not itself need it, including the every-minute cron, so a dashboard call arriving later on that isolate finds the graph evaluated. The import is memoized as a promise so a pre-warm and a real request racing on a fresh isolate share one import; a failed import is not memoized.Expected effect: the
entered=falseshare ofworker.dispatchspans withexecutor.dispatch.plane=appdrops from ~30% toward the fresh-isolate floor (~13%). The truly fresh isolate still pays; that is the graph's own evaluation cost and is a separate change (moving the MCP session Durable Object's imports behind a lazy boundary).Verification after deploy, Axiom,
executor-clouddataset:🤖 Generated with Claude Code