On Fri, Sep 14, 2012 at 8:57 AM, John Stoffel <j...@stoffel.org> wrote:
> > > Andrew> throughout the day, as the sev 1 callout got escalated and > Andrew> different shifts of people got called, i had to re-explain our > Andrew> theory that although the networking folks could not find > Andrew> anything at all, save one link that occasionally had some > Andrew> dropped packets (around 0.1-1%), it had to be an external > Andrew> thing (because all 8 servers go it at the same time) and was > Andrew> most likely the network. we ended up rebooting all teh servers > Andrew> a few times and reloading all the app software, to no avail. > Someone correct me if I am wrong network gurus, but anything hovering around 1% packet loss is actually *really* high packet loss (imagine 1 out of every 100 packets dropped and how many retransmits that can cause). This brings me to my next point. When a segment gets dropped TCP tends to lower the sending window size so that the probability of packet loss/unacknowledged segments in flight is low. If it keeps dropping packets that brings you to the next level of TCP Hell where the Send-Window on the client fills up and the client is like I am waiting for packets to be acknowledged before I put more on the wire.
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
