Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusion about multiple connections #10092

Closed
KamenRiderKuuga opened this issue May 26, 2022 · 1 comment
Closed

Confusion about multiple connections #10092

KamenRiderKuuga opened this issue May 26, 2022 · 1 comment

Comments

@KamenRiderKuuga
Copy link

Since Nagel has been closed as @manzhizhen said, the 40ms delay should not exist, why do we still need this feature

Originally posted by @KamenRiderKuuga in #2457 (comment)

@kimmking
Copy link
Member

Generally, nagle cause a client spent 200ms delay to send data to a server.
And delay ACK cause a server spent 40ms delay to ack client's request data, then following packets will be blocked at least 40ms.
BTW, sometimes TCP Retransmission cause 200ms and then double it in next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants