🤖 Implement SSH connection pooling #453
Merged
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.
Problem
SSHRuntime generated random controlPaths for each instance, preventing SSH ControlMaster from multiplexing connections. This meant every workspace operation opened a new TCP connection to the remote host, even when targeting the same server.
Solution
Replaced random controlPath generation with deterministic hashing based on connection config (host, port, srcBaseDir, identityFile). Identical configs now produce identical controlPaths, enabling SSH ControlMaster to automatically multiplex connections.
Key changes:
sshConnectionPoolmodule with pure function for deterministic controlPath generation (~53 lines)getControlPath(config)instead of random IDsbuildSSHArgs()so git bundle transfers also multiplexdispose()to no-op since ControlPersist=60 handles cleanup automaticallyDesign approach:
Impact
Performance:
Example:
Testing
Generated with
cmux