Skip to content

perf(mcp): reduce Windows startup module resolution - #1814

Merged
N0zoM1z0 merged 3 commits into
mainfrom
perf/windows-startup-packaging-1685
Oct 11, 2026
Merged

N0zoM1z0 merged 3 commits into
mainfrom
perf/windows-startup-packaging-1685

Conversation

@N0zoM1z0

@N0zoM1z0 N0zoM1z0 commented Oct 11, 2026 •

Copy link
Copy Markdown
Collaborator

Windows MCP initialization can exceed the SDK’s default 60-second deadline. The Windows trace investigated in #1685 showed substantial module filesystem resolution.

Bundle REA’s internal MCP modules and route the packaged dispatcher to that entrypoint. Dependencies remain external and dynamic imports remain lazy. Original compiled files stay available to CLI and worker entrypoints; bundled code retains their module URLs for resources, native helpers and package resolution. Unsupported import metadata fails during the build.

Verified at 2bc0dfad7, based on main cdd9fe716:

Windows initialization Original entry Bundled entry
AB pair 35.26 s 9.55 s
BA pair 28.66 s 14.53 s

These are two observed pairs, not a stable latency estimate. Fresh processes used Node 24.18.0, SDK 2.3.1, two CPUs, BelowNormal priority and the unchanged 60-second initialization deadline. All four returned the same 171-tool catalog (1,967,836 bytes, identical SHA-256). First-call client validator compilation remains a separate cost.

Actual offline Windows installation completed through a guarded npm install repair after the bounded npm ci attempt expired. Every installed REA file matches its archive: 1,184 baseline files and 1,251 candidate files. Both packages pass normal SDK session, JavaScript worker analysis and subsequent ping; the full normalized analysis result and Evidence ID match, inputs stay unchanged and owned runtime files/processes are cleaned up. Linux passes the same public workflow. This does not verify Ghidra cold analysis or establish a memory improvement.

build:cached, normal npm pack/prepack, four process/dispatcher regression cases, check:fast, lint and docs checks pass under the 2,304 MiB family limit. Full local typechecking uses the compiler’s single-threaded mode. All 31 exact-head CI checks pass, including native package baselines.

Refs #1685.

@N0zoM1z0 N0zoM1z0 added area: mcp MCP server, transport, and tool registration area: build Build, CI, packaging, and publishing performance Performance regressions, scaling limits, and bounded-resource work labels Oct 11, 2026
@N0zoM1z0
N0zoM1z0 marked this pull request as ready for review October 11, 2026 13:00
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-11T13:03:30.362149Z 2bc0dfa Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@N0zoM1z0
N0zoM1z0 merged commit 76e4153 into main Oct 11, 2026
31 checks passed
@N0zoM1z0
N0zoM1z0 deleted the perf/windows-startup-packaging-1685 branch October 11, 2026 13:01
@github-actions github-actions Bot mentioned this pull request Oct 11, 2026
3 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: build Build, CI, packaging, and publishing area: mcp MCP server, transport, and tool registration performance Performance regressions, scaling limits, and bounded-resource work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant