Registered Member
|
ktorrent-2.0.3
On downloading process complete, I've found that I've downloaded much more than a real size of the file:
Then I've restarted ktorrent, and...
...zeroes, while an upload process takes almost all of my bandwidth =)) Is this a tracker or ktorrent stats problem? |
Registered Member
|
|
Registered Member
|
|
Registered Member
|
|
Registered Member
|
yes restarting the client starts a new session and resets the stats, no problems there, only problem is with over-downloading
*EDIT* Did some more testing on another tracker and for about 350MB downloaded it downloads ~100MB extra.. The weird thing is that ktorrent reports that it only downloaded ~350MB (the size of torrent) but the Share ratio reported in the Status isnt 1.0 even when Uploaded is at ~350MB.. so there are some more bugs here. Im guessing Downloaded is reporting the size of the torrent and not the actual downloaded size. Cheers |
Moderator
|
There are 2 reasons why you could get over downloading :
- Peers sending bad stuff - Multiple peers assigned to one chunk, can cause duplicate pieces being sent But with a normal torrent this shouldn't be that big. I will investigate this in the weekend when I have some downloading to do. |
Registered Member
|
Thanks for investigating this George!
Want to clarify one thing, I did these tests on private trackers where issues with peers sending bad stuff are minimal. Highly unlikely to have peers send ~300MB bad stuff on several different torrents. And like I said before, havent had these problems with other clients on the private trackers at least. Thanks again |
Registered Member
|
|
Moderator
|
Is the chunk size large ? 1 MB, 2 MB ?
There is a limit on the amount of memory we use for chunks we are currently downloading, by default this is set to low which means 10 MB will be used for downloading chunks, so if your chunks are 1 MB large, you can only download 10 simultaniously. If you can download from more peers then 10, ktorrent will assign multiple peers to each chunk. |
Registered Member
|
|
Registered Member
|
|
Registered Member
|
I have the same feeling, because the stats are correct and bad chunks will not take 100MB on 350MB, that's insane. Would be good to know when this bug got introduced, maybe i can do some tests on that today. |
Moderator
|
|
Registered Member
|
|
Moderator
|
I know what the problem is, coming up with a solution which does not impact the download speed, and minimizes the over downloading is the hard part. |
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar