Jump to content

Not a bug, but seems like a defect


Jon

Recommended Posts

Posted

In the advanced options peer.disconnect_inactive_interval. this ignores values below 300 seconds except under certain conditions.

"peer.disconnect_inactive This enables or disables disconnecting from inactive peers after a set period of time (default being 5 minutes). However, it will NOT disconnect if the number of peers in the swarm is lower than the value set for maximum number of connections per torrent." according to the FAQ.

Maybe I'm misunderstanding this, but from what I have read about the protocall it calls for this to be 60seconds as the default, but µtorrent jacks it up to 300 and ignores settings below this unless...

If I was connected to someone that had went inactive for 60 seconds, I would certainly want to use that slot for someone else (whether up or down). Why would you want to wait 5 minutes for an inactive disconnect ? Can anyone clear this up or if I am understanding this correctly change it in the next build so that it uses 1 minute instead of 5.

Posted
peer.disconnect_inactive_interval This sets the time that a peer is allowed to be inactive before being disconnected, except for small swarms. µTorrent ignores values below 300.

Right below the one you quoted. The protocol doesn't actually specify any idle disconnect, it's totally up to the client what to implement (if at all). 60 seconds is far too low for choking/unchoking to do its job. In fact, many people recommend using higher than 5 minutes (15 at minimum).

Reducing this would 1) waste bandwidth (every reconnect uses significantly more bandwidth than being idle) 2) screw with the choke/unchoke function of the protocol 3) reduce YOUR performance. It often takes more than 60 seconds for a peer to unchoke you. Disconnecting too soonwould make YOUR client lose that opportunity.

Posted

Ok it waste bandwidth, but if your only getting 1/2 or less of your possible speed then you have down bandwidth to waste, and if this would increase the speed (by replacing an inactive with an active connection) It seems like it would be worth while. The part I'm missing is: How can no activity for a minute be faster then changing to another peer with activity in a few seconds.

Maybe i'm confusing the peer.disconnect... with another function, (snubbing) Not positive, but I think I was it reading on the bittorrent site as far as the 60 second disconnect part.

Posted

50% or so of the peers i'm connected to are dead peers (they don't upload at all)

each of them is taking a connection (50 is the maximum connections that i can make - determined by the ISP)

if they don't seed i don't want them.. 60 seconds is OK

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...