samples: modbus: tcp_server: improve server latency #89099
Closed
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
Add TCP_NODELAY to disable Nagle's algorithm - significantly reduces server latency Signed-off-by: Petr Vilím <[email protected]>
Add TCP_NODELAY to disable Nagle's algorithm (fixed code formating) Signed-off-by: Petr Vilím <[email protected]>
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.
Add TCP_NODELAY to disable Nagle's algorithm - significantly reduces server latency
When reading or writing modbus registers in continuous mode without closing connection (or port) between each read or write, the server latency increases from few milliseconds to above 50ms. This behavior was observed independently of different hardware configurations, e. g. ESP32-S3-DevKitC-1 (connected by Wi-Fi), XMC4700-Relax-kit or a custom board with Wiznet W5500 + STM32G0B1RE (both connected by ethernet).
After logging packets with Wireshark, cause was found in long delay between client query and server response. Disabling Nagle's algorithm in TCP stack completely solved this issue.