Pérdida de paquetes inducida por TCP sobre las referencias de tesis de UDP y Bachelor

Question

Actualmente estoy escribiendo una tesis de licenciatura en informática e ingeniería, estamos creando un juego de carreras en C ++ con OpenGL.En el informe, estoy comparando el uso de TCP y UDP y encontré un Fuente , que afirmó que las múltiples conexiones TCP pueden inducir la pérdida de paquetes en una conexión UDP.Incluso tengo una buena referencia

El problema radica en el hecho de que tiene 13 años, pero no he podido encontrar ninguna indicación de que cualquiera de los protocolos haya modificado para solucionar este problema.También he incapaz de encontrar papel o artículo, que sean más actuales, que realicen investigaciones similares

Por lo tanto, mis preguntas son si ha habido cambios en los protocolos que pueden ser relevantes y / o si solo debería olvidarse de usar esta antigua referencia en el informe de tesis.

Answer 1

Read the significant points in the article:

1. First, we focused on the case in which only TCP connections use all of the bandwidth of the network.
2. With the increase in the number of TCP connections, a larger number of packets can simultaneously arrive at the node, thereby making the buffer severely congested and thus making packet loss occur more often.

So the WAN link under test is saturated and the testing is for fairness of the TCP and UDP protocols. The 29 West article linked in the comments also notes:

Myth--There is no loss in networks that are operating properly.

Reality--The normal operation of TCP congestion control may cause loss due to queue overflow. See this report for more information. Loss rates of several percent were common under heavy congestion.

None of this is particularly new or should be surprising to anyone. Consider a home Internet connection, DSL or Cable with minimal speed, e.g. 2mb/s and setup one computer with Bittorrent downloading several large files, now try to run a UDP game such as Valve's Team Fortress 2. It's not going to work well.

With VoIP many networking persons started looking at methods to improve this situation which brings QoS to the table. QoS however demands co-operation both ends of the WAN and so this is of no benefit to the majority of end users. The only real solution is bandwidth throttling. If you have a 2mb link you set the TCP traffic to say 1.5mb and leave the remainder for UDP traffic for gaming.

If you are developing a split protocol game you would define a upper bandwidth limit, say 25KB/s per client for the total traffic and then define separate limits for TCP and UDP traffic within that limit, e.g. 15KB/s for TCP and 10KB/s for UDP. Generally games tend to use HTTP (TCP) for downloading game content outside of the game and then switch to UDP inside the game to remove the issue completely.