Transmission

Hi there.

I'm currently seeding one file to exactly one person. Whenever I have µTP enabled the upload speed gets capped at exactly 72KB/s. It doesn't get any higher than that. When I have it disabled I get upload speeds of 130KB/s and more. I do understand that µTP may limit it a little too much but should it really limit it by the half? I have no idea why it thinks that the speed should only be that slow.

Any ideas? I wouldn't think that µTP would slow things down that much, especially since many people report it even being faster sometimes.
The other peer is using µTorrent (2.x or 3.0, doesn't make any difference).

Thanks for any advice,
Farthen

Hi Farthen,

I also recognise some strange behaviour with µtp. I got really interessted in µTP and wanted to play with it in my LAN (Gigabit) . For this purpose I set up a tracker and one seeder. First I started the transmission-daemon with --no-utp option. Consequentially transmission will use TCP. The download only took some seconds and than it finished.

Then I started the transmission-daemon (on both sides) with the --utp option. To check if transmission really uses UDP for its transport protocol I started wireshark to be sure. But this time my downloads does not go faster then 250 kbps. Which is pretty slow in a Gigabit LAN. I tested transmission 2.33, 2.42 and 2.42+ (nightly build).

There is almost no traffic on my network, so it can't be a problem with the foreground traffic. I also set net.core.wmem_max=1048576 and net.core.rmem_max=4194304 according to the logfile but nothing changed. Did you found any solution to you problem or might this be a bug in libutp/transmission?

cit