Jump to content

µTorrent 1.8.5 released


Firon

Recommended Posts

  • Replies 152
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Unlimited upload speed can cause problems. v1.7.7 may not hammer whatever real upload max you have, causing it to drop less in speed when your ISP forcibly corrects it.

So you're allowing up to 50 outgoing peer/seed ip connections at once (net.max_halfopen), and creating 20 new outgoing ones per second (bt.connect_speed). This does not count however fast you're also getting incoming connections. I would imagine all those connection attempts (which use mostly upload) would reduce how much of the torrents you can upload.

The disk cache settings are bizarre. Reduce memory when cache isn't needed? It'd only use 32 MB max, the default max. Disk read caching is completely disabled?

Link to comment
Share on other sites

Switeck, I'm not sure that I'm correctly understand you, I'm not good in English. =(

I set max_halfopen to 50 because is optimal for my line, I can set it to 8 (default) - the effect is only slower peer discovery (I mean period when utorrent just start, get peers from tracker and DHT and then checks what pieces they have) about 1 hour and I have maximum upload speed, if it set to 50 discovery will take about 20 minutes, however in uTorrent statistics shown that there only 20-30 half-open connections at any time.

What's for disk caching - I'm just want shorten disk queue, so I think with diskio.coalesce_writes enabled it give good results. Yes, disk read caching is disabled, I never seen that it's used, so I think it will give a bit lower cpu usage.

Link to comment
Share on other sites

It's not a "slow peer connection" issue, it's just a normal limit on how fast it can open new connections imposed by older Windows. :P It'll take a lot longer at program startup because it has to scrape all the stopped/queued torrents, as well as do the announce for all the started torrents.

Link to comment
Share on other sites

> Your upload speed maxes out around 60 KB/sec?

Amm, no, I'm just disable upload speed limit, as you say there is only limit on ISP side. I can forcibly set limit to 48 KB/sec (ISP speed) but it will take no effect. uTorrent shows 39-43 KB/sec, and it stable on all upload period.

> Do you always get a green light (unfirewalled) in uTorrent?

Yes, port on router forwarded manual. UPnP also enabled so there is no problem.

Link to comment
Share on other sites

No, connecting... updating... countdown update timer, on tracker site statistics also updated information, DHT and Peer Exchage looks like work too.

I'm just see that other users have similar problem.

I don't know may be it don't matter but I see how peers connecting and then immediately disconnects even when they have less 10% done, I think in normal case they must connect and start downloading of course if they not reach connections limit and other conditions, but looks like they don't understand or simply ignore me, it's happening even with torrents that have more than 40 peers and seeds/peers ration close to 1.

Link to comment
Share on other sites

I'm also having problems with https trackers...seems like the same problem jeps96 and teix posted. I noticed "can't unzip" tracker status on some torrents for a certain https tracker. The weird thing is that it doesn't happen for all torrents from that tracker, just some. And, yes, they all have the same tracker url (https). Which brings me to a question: Does µTorrent "fall back" to http when a https tracker isn't working? Because that's exactly what seems to be happening. I get "can't unzip" in the https tracker status and the torrent has a red icon next to it, and yet it still gets the seeds and peers from the tracker and downloads normally. This particular tracker works with both http and https and when I change the https to http manually, the status changes to "working" but like I said even with the https it still works, just says "can't unzip" in the status.

P.S. Torrents tested are from a private tracker so DHT, LPD, PE are all "not allowed" and there is just the one https url in the trackers list.

OS: Windows 7 Ultimate x64

µTorrent 2.1 alpha (build 17085)

Link to comment
Share on other sites

I am running WIN7 64bit Professional.

Somme additional information (could be relevant)

After running µTorrent for about 100 hours, there seems to be an increasing number of connection (attempts?) getting stocked. I end up having 7 half open connections and 7 TCP connecting.

Normally I would have less than 3. The result is slowing down the upload speed because no new peers can connect.

It looks a bit like the https thing (- Accounting of half open https connections would cause uT to stop making new connections) is not completely fixed or maybe something of the similar is happening to http connections too?

Link to comment
Share on other sites

Step said, "I don't know may be it don't matter but I see how peers connecting and then immediately disconnects even when they have less 10% done"

...is a classic example of an ISP disrupting BitTorrent traffic.

A bad/misconfigured software firewall or bad networking hardware could remotely cause this too.

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...