Repository navigation
Enable TCP_NODELAY on connections - #149
Merged
Merged
Conversation
kelunik
approved these changes
Nov 1, 2026
Member
|
Thanks! |
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.
Fixes #55
COM_STMT_CLOSEgets no reply from the server. With Nagle's algorithm enabled, the next command then stays in the client kernel until the server acknowledges the close packet. That's typically theCOM_STMT_PREPAREof the nextexecute(), and Linux delays the ACK by 40 ms. mysqlnd setsTCP_NODELAYright after connecting, which is why PDO and mysqli don't have this issue.On MySQL 8.4,
execute('SELECT ?', [1])goes from 44 ms to 1.5 ms per call. Found while profiling the AMPHP SQL transport of Symfony Messenger (symfony/symfony#67521).