Repository navigation
Configure TCP Socket to Prevent Transmit Delay - #16
Merged
Merged
Conversation
lsigrist
force-pushed
the
optimize-tcp-connection-config
branch
from
September 10, 2026 13:22
d86584f to
04b1ea4
Compare
lsigrist
changed the title
psachs
approved these changes
Sep 22, 2026
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
3 participants
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.
Enables TCP_NODELAY options on the TCP socket for SHDLC communication to remove Nagle as potential latency contributor.
Background
This setting disables Nagle's algorithm that delays to combine potential additional data into a single TCP frame transmission. With the relayed SHDLC protocol following a strict command/response scheme and the transmit path submitting the full frame in one socket send, it is guaranteed that no additional data follow any send of a command frame. Disabling Nagle allows immediate transmit of the command frame without potential wait for additional data.
Expected Benefit
Close to zero latency reduction, as with command/response scheme Nagle should not delay transmit on idle connection. Disabling Nagle makes immediate send explicit, documents it, and prevents Nagle being a source for unexpceted (future) latency increase.