https://bugzilla.mindrot.org/show_bug.cgi?id=2848
--- Comment #2 from Thanassis Tsiodras <[email protected]> --- @Kristian: Unless I am mistaken, that post argues from the other side - that of a fast link, where they *want* to disable Nagle. As you can see in my case (slow wifi link), enabling Nagle dramatically increases the transfer bandwidth... ...which basically reinforces why we need to have this option as a user-configurable one: as is right now, the call to setsockopt that enables TCP_NODELAY is unconditional. IMHO it shouldn't be - the end-user should be able to control this, so that when SSH is used for transport, users with fast links can choose to disable Nagle - and users like me (with slow links) can enable it and avoid wasting bandwidth by sending half-empty packets. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
