Repository navigation
Conversation
ameba23
added this pull request to stack #185
October 2, 2026 08:02
ameba23
force-pushed
the
peg/connection-pool
branch
from
October 6, 2026 09:01
fcb30de to
8634c61
Compare
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.
Adds an optional warm connection pool to the TCP tunnel client, reducing connection setup latency by preparing TLS and attestation ahead of source connections.
This means that when it is configured, client connections do not need to wait for TLS handshake or attestation.
It is disabled by default - a pool size of zero preserves existing behavior.
It has configurable pool size, maximum connection age, and refill concurrency.
Connections to the target service are immediately opened and held open. This is something i might change. For gRPC we probably don't want this - we can connect to the target service as soon as the source client sends a request, and this would probably make things simpler. But worth noting that for protocols where the server speaks first (eg: SSH) this wont work, as the server can start sending data before there is a client who will receive it.