48,001 reputation
27153310
bio website kbrandt.com
location Hollywood, FL
age 32
visits member for 5 years, 4 months
seen 13 hours ago

After about a year of being a member of the community I am now Stack Overflow Valued Associate #9 (Or Server Fault Valued Associate #1 if you like).

Besides trying to keep these sites up I will also be writing posts for the [Server Fault Blog][2].

[2]: http://blog.serverfault.com/

@KyleMBrandt


Jun
30
revised Windows TCP Window Scaling Hitting plateau too early
added 102 characters in body
Jun
30
revised Windows TCP Window Scaling Hitting plateau too early
added 3 characters in body
Jun
30
revised Windows TCP Window Scaling Hitting plateau too early
added 326 characters in body
Jun
30
comment Windows TCP Window Scaling Hitting plateau too early
@SmallClanger: Another guess, try playing with netsh int tcp show heuristics / netsh interface tcp show heuristics disabled|enabled
Jun
30
revised Windows TCP Window Scaling Hitting plateau too early
added 172 characters in body
Jun
30
comment Windows TCP Window Scaling Hitting plateau too early
@SmallClanger: Oh, and to help clarify, my graph if I understand it correctly displays the RWIN as it currently is over time. In other words, it is "currently available bytes" in the buffer. So the RWIN always has plenty of space.
Jun
30
revised Windows TCP Window Scaling Hitting plateau too early
added 202 characters in body
Jun
30
comment Windows TCP Window Scaling Hitting plateau too early
@SmallClanger: Also look at "Expert Analysis" in the two captures. In the Linux-to-Linux one, you see Zero window messages, duplicate acks etc. This is actually what one would hope to see as TCP gets pushed to its limit and then enforces some flow control. In the Windows to Linux case, everything is clean because TCP isn't "stress tested".
Jun
30
comment Windows TCP Window Scaling Hitting plateau too early
@SmallClanger: Regarding "Could there be some other reason that Linux is artificially limiting the RWIN?". I'm not positive, but I would agree with your theory that the RWIN doesn't increases because it is never getting low. It would be silly to do so, because that would mean more memory usage when there is no reason to take more memory for the receive buffer.
Jun
30
revised Windows TCP Window Scaling Hitting plateau too early
added 523 characters in body
Jun
30
answered Windows TCP Window Scaling Hitting plateau too early
Jun
30
awarded  Popular Question
Jun
29
comment Windows TCP Window Scaling Hitting plateau too early
Any chance of putting up some packet captures from one of the slower senders somewhere?
Jun
26
revised How far is “too far off” for ntpd? Can it get there by a sudden jump to heavy load? Can this be overridden?
added 92 characters in body
Jun
26
answered How far is “too far off” for ntpd? Can it get there by a sudden jump to heavy load? Can this be overridden?
Jun
26
answered Exclude named pipes and sockets in Puppet
Jun
25
awarded  Announcer
Jun
25
awarded  Notable Question
Jun
25
answered Change from 192.168.x.x to 172.22.x.x
Jun
25
awarded  Nice Question