This repository was archived by the owner on Nov 8, 2020. It is now read-only.
Set TCP_NODELAY on the RethinkDB connection to avoid Nagle's algorithm delay#15
Open
ddfisher wants to merge 1 commit intonpiv:masterfrom
Open
Set TCP_NODELAY on the RethinkDB connection to avoid Nagle's algorithm delay#15ddfisher wants to merge 1 commit intonpiv:masterfrom
ddfisher wants to merge 1 commit intonpiv:masterfrom
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We were seeing simple local gets (which should have taken ~1ms according to the query profiler) take ~40ms with this driver. @danielmewes suggested setting TCP_NODELAY on the SocketChannel to avoid delays caused by Nagle's algorithm. This fixed our problem.
This fix should be strictly positive for response times.