INTERESTED flag being incorrectly cleared when...

[Zoz]

Greets,

Sorry, but this is a topic being somewhat discussed in another forum, but not apparently understood, confirmed, or otherwise getting any attention:

http://forum.utorrent.com/viewtopic.php?pid=157366#p157366

uTorrent is dropping its INTERESTED flag after every piece superseeded to it by Azureus clients. About one minute later, uTorrent turns the flag back on and Azureus sends the next piece. Rinse & repeat adinfinitum.

This results in a tremendously inefficient use of time and planned bandwidth allocation for uTorrent users.

Thanks for taking a peek at this...

[1c3d0g]

Hmm...very interesting. This might explain some users' complaints regarding µTorrent not being very "aggressive", particularly in poorly-seeded torrents... :|

[Zoz]

I did some more research and found that uTorrent seems to be waiting an awful long time sending the BT_HAVE piece message:

This is an Azureus log to a uTorrent client:

[10:32:02.666] {net} Received [bT_REQUEST piece #986:2080768->2097151] message;

[10:32:03.525] {net} Sent [bT_PIECE data for piece #986:2031616->2047999] message;

[10:32:04.541] {net} Sent [bT_PIECE data for piece #986:2048000->2064383] message;

[10:32:06.213] {net} Sent [bT_PIECE data for piece #986:2064384->2080767] message;

[10:32:07.431] {net} Sent [bT_PIECE data for piece #986:2080768->2097151] message;

[10:32:09.900] {net} Received [bT_UNINTERESTED] message;

[10:32:17.010] {net} Sent [bT_CHOKE] message;

[10:32:54.135] {net} Received [bT_HAVE piece #986] message;

[10:32:57.635] {net} Sent [bT_HAVE piece #993] message;

[10:32:58.978] {net} Received [bT_INTERESTED] message;

[10:32:59.994] {net} Sent [bT_UNCHOKE] message;

[10:33:00.244] {net} Received [bT_REQUEST piece #993:0->16383] message;

That's over 45 seconds! Other clients send the BT_HAVE within 1 second. This example file is 4GB. Is the piece and file so large that uTorrent handles the save poorly and takes 45 seconds to save it?? I haven't experimented with a smaller file and uTorrent.

Based on this, I s'pose the thread topic should be "Why does uTorrent take 45 secs to ack a received piece from a super-seeding Azureus client?"

[Firon]

And are you testing with beta 428? As the sticky says, anything reported for earlier builds is ignored.

[Zoz]

uTorrent clients I'm experiencing this with is the version posted as STABLE on your home page (1400).

I've moved the data to the Troubleshooting thread. Feel free to lock/delete this thread.

Thanks!

[Firon]

Like the sticky says, any report that's not done with the latest beta build is ignored.

More than half the time, what people mention has already been fixed. This is one of them.