Registered Member
|
I think connecting to so many peers is not really the problem. Each peer you are connected to represents overhead, and so with my relatively slow link I tend to want few peers. With rufus or bittorrent or azureus or rtorrent, downloads proceed efficiently (in even contention torrents 50seeds, 50 leeches, or so), with only 10 or so peers.
Ktorrent often seems to have a lot of trouble achieving steady throughput with these few peers. I do not know what the issues is exactly, but it seems something could use tuning here. |
Registered Member
|
someone said it good in the posts above; kt somehow chokes on public trackers.
I guess it needs to be more aggressive on public trackers: monitor and swap peers and cache the fast seeders since pub trackers tend to have many peers and most of them are bad seeders compared to the private trackers. One easy way here is to check the source of other clients that dont have these problems and see how they are doing things. Cheers |
Registered Member
|
|
Registered Member
|
Damn, I forgot this topic. I dunno how this looks to others, and the state of a torrent somewhat changes over time too... but after some period of use, it looks to me that this did something good to the process of getting a connection; both on public torrents but also as a seeder on the private torrents when there are many seeders and only a few leechers. I hope this looks the same for other people.
I don't think this will do us any good. But that again is my biased opinion. |
Registered Member
|
I think he meant it as a joke As I look around the average swarm, Az and uT seem to be equally popular... arguably uT a bit more prevalent. Either one is well worth implementing. The download performance has gotten a lot better since I began to complain about it with the 2.0 series. Now, 2.0.3 delivers very acceptable download performance, and 2.1svn is even better |
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar