This repository has been archived by the owner on Dec 7, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 87
Conversation
This file contains 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
Looks like it's failing ... be right back. |
If you can push again (perhaps edit a commit message and force push) it should trigger the build again |
✅ |
Seems good, thanks! |
tarcieri
added a commit
that referenced
this pull request
Jul 8, 2013
Disable Nagle's alrogithm by default.
I've already been using that in my branch, however I also have these. Ought I push them into a pull request?
|
REUSEADDR would be good. I don't think that usage of TCP_CORK alone will work, though |
Ok I will do that. TCP_CORK works with TCP_NODELAY but both or one of them are linux only so I trap by OS. |
I don't get how TCP_CORK works if you're never uncorking |
I believe |
That doesn't help unless you've corked... |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For a webserver where requests/responses are usually large enough to be contained in a packet, the Nagle's algorithm slows the last packet sent.
This configuration is probably used in most ruby web servers. I only checked for Puma though.