This will almost certainly speed things up, though who could say definitely the problem you have? I don't know if you have dnsmasq or bind9, but it won't hurt to try to uninstall them. I have experienced that problem, which I fixed by running my own DNS cache. Windows XP isn't affected, because it's got other limits on outgoing data and can't saturate lines like Linux & other more modern OS's can. The "feedback loop" is delayed by the size of the buffers. By having a huge transmit queue, the queue delays any adaptation the TCP stack would make, and you get these huge latencies and bad throughput because you're sending more data than the network can handle. When it encounters these situations it sends out less data to better adapt to the network. The short version of what this does - TCP expects packets to be dropped and/or not acknowledged in a timely manner. (Almost every modern chipset will support 0, but some don't, so we'll go with 50 for safety reasons).Īs of note, this MAY bump you off the network temporarily - you may need to force your machine to reconnect to the network (unplug/replug cable, sudo ifconfig eth0 up, etc.) Lower the size of your transmit buffer to 50. The default on almost every machine I've seen is 1000. Run ifconfig and look for "txqueuelen" in it. It manifests itself as huge latencies when you're transmitting or receiving a lot of data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |