![]() As the screenshots show, Vuze has the same behavior. > How are other clients able to control this global transfer too? As a visual aid I've added a horizontal green line showing the "ideal" of where a constant 15 KB/s would lie on each g-s-m network graph. So I've spent the last 45 minutes doing snapshots of different BitTorrent clients to demonstrate that this behavior in all BitTorrent clients, not a simple Transmission bug.Įach screenshot shows a different BitTorrent client downloading the same Ubuntu ISO torrent with speed capped at 15 KB/s both ways, next to a gnome-system- monitor showing overall network use. ![]() Setting as wontfix instead since the intent seems to just close this bug.ĭaniel Lee gave an intelligent explanation about why the amount of piece data being transferred isn't the same as the overall network footprint, and you dismissed this as "hand waving." and saying that the user needs to prove it is transmissions fault! Setting as wontfix instead since the intent seems to just close this : It is sad to see this bug is being hand-waived without actually giving us steps to debug the issue. Its just lack of interest in debugging from the transmission devs. No debug info was requested, so not incomplete. We are facing the bug and we have provided the info we can. ![]() If transmission devs dont want to fix the issue, it's up to you folk.īut mentioning it as an invalid bug is wrong. Vuze does this very well, if we set a global limit then it *is* honored. How are other clients able to control this global transfer too? Then what is the purpose of having a global limit if it cannot control global transfer? The problem here is not the over-head, but why isnt transmission trying to control the overhead even when we explicitly set the global limits? If we knew about torrent protocols and if we knew how to debug, wouldnt we let you know already? There are screenshots of users facing the problem that is the info *we* can provide. ![]() Why dont you try to give us some steps to debug this issue? and then tell us its not transmission's fault! ![]() : It is sad to see this bug is being hand-waived without actually giving us steps to debug the issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |