Sweep idle UDP connections#593
Open
redneck-f25 wants to merge 1 commit into
Open
Conversation
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.
When sending many UDP datagrams from many clients (every 10 seconds from 3500 clients), I ran out of available ephemeral ports.
(connections are now kept alive as long as there is traffic in either direction)
EDIT 2026-07-01
Today I used the patched version in the field and provide some real-world numbers for comparison.
Every 5 seconds, the TCP (WebSocket) connections established by Chisel clients to the Chisel Server (via a TLS-Offloader) and UDP sockets from the Chisel server to the receiving service were counted.
The average number of UDP sockets per TCP connection has been reduced from 4.5 to 1.5. Furthermore, the rate remains stable during the measurement period, and the resources required are therefore predictable.