New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: performance figures #124
Comments
Often libtorrent-based uTP struggles to reach half its TCP speeds, so yeah...those are valid results. |
I maintain a Go torrent client that uses libutp extensively. I can anecdotally report from my own experience, and that of others that uTP does not necessarily provide the same throughput that TCP can. Of course there are other benefits and reasons for this which are reasonable. |
Is testing via loopback a realistic though? ~0 latency, very high bandwidth and packet losses that don't reflect the behavior of physical links. I guess it stresses different parts compared to WAN connections for which utp is intended. That said, those speeds still seem low for such an idealized connection. |
@the8472 I've tested with someone a couple continents away with some built-in packet loss and very high latency. I resorted to using mostly (but not always) 127.0.0.1 local loopback because it's easy and quick to set up compared to the coordination needed to do the others. |
Hi,
Do you have any performance figures comparing libutp to TCP?
I've found this https://maidsafe.atlassian.net/browse/MAID-3221?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel and the results mostly match what we've got running ucat ourselves, libutp being about half fast as TCP. But I'm shocked by the results, I expected libutp to be much faster, so I bet ucat is not valid for a real benchmark, am I mistaken?
The text was updated successfully, but these errors were encountered: