![]() Registered Member ![]()
|
On one of my torrents right now, I've downloaded 600MB but uploaded around 1400MB. Is this normal behavior for bittorrent and a swarm where there's few seeds but a lot of peers? Or is some client taking advantage of ktorrent?
|
![]() Registered Member ![]()
|
I think it's normal when the other peers do not upload that fast into swarm. I don't think there are any wholes in the protocol for that matter we can go around, other than speed limiting from client side. But maybe i am wrong... (never say never
![]() But i notice this too now and then, and it's almost like other users limit their upload, probably after they take notice the progress in swarm isn't that fast. I think this would be a reason where per torrent speed limiting could be in handy. |
![]() Registered Member ![]()
|
Hmm... I have opposite problem with Ktorrent.
I'm mostly downloading from privte tracker, where ratio is very important. Thus there're many seeders and lack of leechers. Ktorrent has problem with uploading: 300-400MB max per day, but in Azureus on the same torrents I can upload over 1GB per day. That makes I can't use Ktorrent all the time - I would have lost my account because of low ratio ![]() |
![]() Moderator ![]()
|
Have you tried playing with the number of upload slots ? |
![]() Registered Member ![]()
|
I have 10 upload slots, which looks similar to Azureus settings measured by eye (it's config window is so mess, that I couldn't find that)
I've tried setting it to 5 and 15, but didn'r see any changes. Today I've made another test: Seeding 11 torrents both on Azureus and Ktorrent for 4 hours. Results: Azureus Time: 13:130 - 17:30 Seeders: 802 Peers: 72 Seed/Peer ratio: 11.13 Uploaded data: 387 MB KTorrent Time: 18:00 - 22:00 Seeders: 758 Peers: 48 Seed/Peer ratio: 15.9 Uploaded data: 200 MB All the numbers were taken at the end of te test. I've noticed, that for the first 1-1.5 hour KTorrent was so fast as Azureus. At the end of the test KTorrent has granted 5 upload slots: 4 out of 5 had set 6th column to yes and 5 out of 5 had set 7th column to yes (sorry, don't know how to translate that columns to english ![]() To get more accurate stats, tommorow I'll try to do the test again. |
![]() Registered Member ![]()
|
this could be because ktorrent correctly sets TOS, while azureus often doesn't (depending on os and java implementation).
If your isp is handling TOS wrongly (TOS in ktorrent is set to maximum throughput, which should send the data through low latency, high bandwidth routing) this could be the problem. |
![]() Registered Member ![]()
|
How can I check if TOS is working correctly in Azureus? Other thing is, that I found this setting:
So I set it to 0x08 and will see if it does a difference... Earlier I tred to set to set upload slots to 5 in KTorrent. Results: KTorrent running 13:50-15:50 sent 120MB Azuerus running 18:00-22:00 sent 243MB. BTW, I've just found 'upload slots' setting in Azureus ![]() |
![]() Registered Member ![]()
|
|
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
|
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
Just to chime in, I too have noticed while seeding Edgy Eft beta ISO's that KTorrent is not nearly as aggressive in seeding as Azureus or even the Python bittorrent/bittornado clients.
KTorrent uploads for a 30 seconds, goes silent for 10 seconds, then start uploading again, and so on, while Azureus is more or less constantly pumping data out. |
![]() Registered Member ![]()
|
how are you monitoring bandwidth? Azureus'es bandwidth monitoring atleast takes an average over longer time than ktorrent does, so it looks more constant, but in reality isn't. |
Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]