Peer to Peer traffic currently stands for a portion of the global traffic on the internet, and uses TCP as its transport protocol. TCP requires packet loss to detect congestion, which means a degradation in services needs to occur before TCP can act. This is why BitTorrent Inc created μTP, to try and mitigate the impact P2P applications have on other traffic. μTP detects congestion with the help of one way latency and can use this to avoid interfering with other flows. This means that it only uses the left over bandwidth.

In this report, we use a physical network to analyze how μTP manages to avoid having an impact on other traffic by only utilizing left over bandwidth. Using μTorrent with μTP we can see the impact on FTP traffic in comparison with μTorrent using TCP. The measure-ments were made at 2 Mbps, 5 Mbps, 8 Mbps and 10 Mbps, all with FTP taking 25 %, 50 % or 75 % of the bandwidth, leaving the remainder as left over bandwidth. By also measur-ing the one way latency we found that when it's consistently below 100 ms, μTP stops yielding to other traffic. This happens at 8 Mbps when FTP takes up 75 % of the band-width and all of the 10 Mbps measurements. We conclude that μTP functions well at lower speeds, having a small impact on the FTP traffic, but stops functioning at higher speeds and instead have a worse impact on the FTP traffic than μTorrent with TCP.