Skip to content

perf(daemon): use native loopback for Linux-local state - #41

Merged
Horcag merged 1 commit into
perf/vm-operation-throughputfrom
perf/direct-vm-transfer
Oct 24, 2026
Merged

Horcag merged 1 commit into
perf/vm-operation-throughputfrom
perf/direct-vm-transfer

Conversation

@Horcag

@Horcag Horcag commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

Linux-local daemon traffic can cross a forwarded IPv4 loopback path under WSL. Prefer native IPv6 loopback for positively identified Linux-local state, with IPv4 fallback. Native Windows, shared Windows-backed state and uncertain mount inspection keep IPv4; explicit addresses bind exactly as requested. Generated bootstrap wrappers use automatic selection while retaining the documented old-controller upgrade procedure.

Add decision tests for platform/state classification, address fallback and rejection, native Windows launcher argument/console behavior, and a pinned binary SSH benchmark comparing IPv4/IPv6. Document measuring the operator-provisioned direct guest endpoint separately from host TCP forwarding.

Validation: full make quality passed, coverage 85.9%, independent code/security and architecture reviews clear. Both actual native Windows wrapper cases executed and passed. Live installed validation combined the directly verified guest endpoint with the new Linux-local listener: a 1 GiB upload took 8.72 seconds of daemon operation time and 19.58 seconds for the complete MCP call, versus 40.93/48.84 seconds before. SHA-256 matched and the exact guest artifact was removed with observed absence. The direct-route-only intermediate result was 12.71 seconds of daemon time.

Shared-state IPv4 compatibility and existing SSH authentication, ownership and receipt boundaries remain intact.

@Horcag
Horcag merged commit 12d9249 into perf/vm-operation-throughput Oct 24, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant