jascape.blogg.se

remote desktop, SSH &c.) will stutter and lag heavily.

Actually, the HTTP request packet was timely sent by the browser, but as it is multiplexed with a shitload of WTs P2P traffic in the router's buffers, a rather large delay occurs between the TCP handshake and the HTTP request.ĭNS requests will be affected - name resolving will be slow and some requests may even time out. if there is even a small delay between your browser connecting to such a server and sending an actual HTTP request they will simply drop the connection. Now, a lot of big web servers nowadays are imposing harsh limits on idle connections, so e.g. So when WarThunder's bittorrent client spawns hundreds upon hundreds of TCP connections, the poor router cannot distinguish between that traffic and traffic that is actually important, and queues them all together in it's buffers, in the order they come in. Longer explanation coming up.Ĭurrently, most of the routers used in home/SOHO environments aren't really capable of handling a large number of concurrent connections properly, i.e. In short, it seems to be a network congestion issue. I saw that a couple of times with the War Thunder updater, so let me try to put my finger on what might be causing issues for some people and how they could go about improving the situation.