Open
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
currently when sending wss requests through pingora, the rtt of a connection lifecycle + sending/receiving a request is ~1300ms compared to baseline ~300ms wss requests through caddy. The additional 1000ms comes from the websocket close handshake (which sends a close frame and waits for server's close frame reply). this exclusively happens in pingora. This takes 1s because the close frame gets buffered until tcp connection timeout. Caddy doesn't have this issue because it flushes immediately for proxied websocket data.
this patch fixes the issue by flushing wss requests immediately:
