Re: FreeBSD Port: ktorrent-3.1.6_1
Does anyone have any ideas of what to look into? I'm about to decide Wine+uTorrent would be an easier route than trying to get ktorrent to work decently. I've tried ktrace again but all I seem to find in it are reads, and a ~1 second ktrace is >4MB. Jonathan Jonathan wrote: > Nikolay Tychina wrote: >> Hello, >> >> i installed ktorrent3 and it seems to be very slow while checking pieces. >> (~2mb per second) >> (Deluge do it much more faster, i didn't try any other clients though) >> Do you have the same problem? > > Same issue here. > > I get ~4MB/s or so. > I started digging around and found that according to gstat (output at > end) ktorrent is writing 50-60MB/s to ad18, which is my boot drive, > sustained. Most of the other drives in the system are completely idle > and belong to the ZFS pool the torrent data is actually on. > > I've checked using fstat and lsof and nothing leaps out at me. I also > watched disk and swap space usage during the check and see nothing > changing despite the apparent massive write load. I even tried doing a > ktrace + kdump and searching for "write" but didn't find anything there > either. I don't claim to be any expert with any of those tools though. > > Does anyone have any ideas on what to look at next? > > Thanks, > Jonathan > > dT: 1.035s w: 1.000s > L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name > 0 0 0 00.0 0 00.00.0| ad8 > 0 0 0 00.0 0 00.00.0| ad8s1 > 0 34 0 00.0 32 430.55.1| ad16 > 0 0 0 00.0 0 00.00.0| ad8s1a > 0 0 0 00.0 0 00.00.0| ad8s1c > 0 0 0 00.0 0 00.00.0| acd0 > 1 3684 0 00.0 3684 589210.2 81.8| ad18 > 1 3684 0 00.0 3684 589210.2 83.2| ad18s1 > 0 36 0 00.0 34 392.19.2| ad10 > 0 29 0 00.0 27 331.17.9| ad12 > 0 34 0 00.0 32 430.45.5| ad14 > 1 3684 0 00.0 3684 589210.2 85.8| ad18s1a > 0 0 0 00.0 0 00.00.0| ad18s1b > 0 0 0 00.0 0 00.00.0| ad18s1c > 0 34 0 00.0 33 833.06.0| da0 > 0 0 0 00.0 0 00.00.0| ad20 > 0 37 0 00.0 36 783.46.9| da1 > 0 36 0 00.0 35 832.35.9| da2 > 0 41 0 00.0 40 693.47.6| da3 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
Chuck Robey wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jonathan wrote: >> Your problem is not related to the one I and the others have. Your >> problem is caused by your upstream being so saturated with data packets >> that the acknowledge packets for the downloads are being delayed or >> dropped. A much more detailed description and more general solution can >> be found here http://www.benzedrine.cx/ackpri.html > > You may be right, I said I didn't understand, but if my upload was supposedly > satured, it makes less sense to me that it never showed as using more that > about > 10K (5K for the average, really) and my limit (for both upload & download) was > set to -1 (infinite). I didn't see why that would cause saturation, although > the other results (having the download rate go from very limited to a max > value) > do kind of support such an idea. Why would my setting the rates both to > infinite cause saturation? > > Or is maybe the upload rate that's being set being only affecting one use of > upload, but not all uses of upload? That could be twisted in that direction, > I > guess, choking off the ability to use uploads for acks, because it's all being > reserved for some other use? Boy, that surprises me, but it's it's what's > meant, it could explain things. If I understand this paragraph correctly, yes, that's exactly what happens. If you check the link I sent earlier it has a detailed explanation with graphs. Jonathan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan wrote: > Chuck Robey wrote: >> I finally found an odd fix, not sure why it worked this way, but I thought to >> pass it along on the hope that maybe it will work for you as well as it did >> for >> me. My max upload is about 38KBPS, my max download is about 160KBPS. I'd >> set >> for to -1, so that the u/d rates would be set to infinite, so that the >> torrent >> client would intelligently choose the best rate. But my experience showed >> that >> my max ACTUAL gross download was only about 25KBPS (remember, I was >> expecting, >> from the torrent protocol, to get better than 6 times that.) >> >> Well, finally losing all hope, I decided to set the upload rate down to about >> 20K, so I could use the reserved rate for other entertainments. IMMEDIATELY >> upon limiting the UPLOAD rate to 20K, the download rate shot up to nearly my >> 160K maximum. I can't understand this, but I tried to move the >> upload/download >> rates around a little bit, to verify the finding: that I just should NEVER >> set >> the rates to infinite, and that (at least in ktorrent) the max download rate >> really was attainable. >> >> I haven't any idea why this worked for me, only that it did do this, >> reliably. >> I may go back to trying previous torrent clients now. What a fine way to >> spend >> the afternoon! > > Your problem is not related to the one I and the others have. Your > problem is caused by your upstream being so saturated with data packets > that the acknowledge packets for the downloads are being delayed or > dropped. A much more detailed description and more general solution can > be found here http://www.benzedrine.cx/ackpri.html You may be right, I said I didn't understand, but if my upload was supposedly satured, it makes less sense to me that it never showed as using more that about 10K (5K for the average, really) and my limit (for both upload & download) was set to -1 (infinite). I didn't see why that would cause saturation, although the other results (having the download rate go from very limited to a max value) do kind of support such an idea. Why would my setting the rates both to infinite cause saturation? Or is maybe the upload rate that's being set being only affecting one use of upload, but not all uses of upload? That could be twisted in that direction, I guess, choking off the ability to use uploads for acks, because it's all being reserved for some other use? Boy, that surprises me, but it's it's what's meant, it could explain things. > > -- > Jonathan > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmZre8ACgkQz62J6PPcoOkCNACgg9KLcYQPqfMt7PSnNzGxIR4N 4esAnjz53tOMiKIGUAQmXzHonyUeDAi2 =FKsT -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
RW wrote: > On Fri, 13 Feb 2009 16:21:32 +0300 > Nikolay Tychina wrote: > >> Hello, >> >> i installed ktorrent3 and it seems to be very slow while checking >> pieces. (~2mb per second) >> (Deluge do it much more faster, i didn't try any other clients though) >> Do you have the same problem? > > Do you have any particular reason for doing this? I only ever do it > when I'm importing a file that I already have into an incomplete > torrent, so that ktorrent can verify the new chunks. That's exactly what I'm doing. In my case I'm trying to import a 157GB torrent and it's only going at 4MB/s which is far too slow. My ZFS array can sustain 100MB+ without a problem so something is wrong with ktorrent most likely. Jonathan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
On Fri, 13 Feb 2009 16:21:32 +0300 Nikolay Tychina wrote: > Hello, > > i installed ktorrent3 and it seems to be very slow while checking > pieces. (~2mb per second) > (Deluge do it much more faster, i didn't try any other clients though) > Do you have the same problem? Do you have any particular reason for doing this? I only ever do it when I'm importing a file that I already have into an incomplete torrent, so that ktorrent can verify the new chunks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
2009/2/13 Max Brazhnikov > > Do you mean 'Check data' for downloaded files? It gives me about 20Mb/s > I mean downloaded data checking, right. Download/upload speed is fine. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
Chuck Robey wrote: > I finally found an odd fix, not sure why it worked this way, but I thought to > pass it along on the hope that maybe it will work for you as well as it did > for > me. My max upload is about 38KBPS, my max download is about 160KBPS. I'd > set > for to -1, so that the u/d rates would be set to infinite, so that the torrent > client would intelligently choose the best rate. But my experience showed > that > my max ACTUAL gross download was only about 25KBPS (remember, I was expecting, > from the torrent protocol, to get better than 6 times that.) > > Well, finally losing all hope, I decided to set the upload rate down to about > 20K, so I could use the reserved rate for other entertainments. IMMEDIATELY > upon limiting the UPLOAD rate to 20K, the download rate shot up to nearly my > 160K maximum. I can't understand this, but I tried to move the > upload/download > rates around a little bit, to verify the finding: that I just should NEVER set > the rates to infinite, and that (at least in ktorrent) the max download rate > really was attainable. > > I haven't any idea why this worked for me, only that it did do this, reliably. > I may go back to trying previous torrent clients now. What a fine way to > spend > the afternoon! Your problem is not related to the one I and the others have. Your problem is caused by your upstream being so saturated with data packets that the acknowledge packets for the downloads are being delayed or dropped. A much more detailed description and more general solution can be found here http://www.benzedrine.cx/ackpri.html -- Jonathan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Max Brazhnikov wrote: > On Fri, 13 Feb 2009 16:21:32 +0300, Nikolay Tychina wrote: >> Hello, >> >> i installed ktorrent3 and it seems to be very slow while checking pieces. >> (~2mb per second) >> (Deluge do it much more faster, i didn't try any other clients though) >> Do you have the same problem? > > Do you mean 'Check data' for downloaded files? It gives me about 20Mb/s I finally found an odd fix, not sure why it worked this way, but I thought to pass it along on the hope that maybe it will work for you as well as it did for me. My max upload is about 38KBPS, my max download is about 160KBPS. I'd set for to -1, so that the u/d rates would be set to infinite, so that the torrent client would intelligently choose the best rate. But my experience showed that my max ACTUAL gross download was only about 25KBPS (remember, I was expecting, from the torrent protocol, to get better than 6 times that.) Well, finally losing all hope, I decided to set the upload rate down to about 20K, so I could use the reserved rate for other entertainments. IMMEDIATELY upon limiting the UPLOAD rate to 20K, the download rate shot up to nearly my 160K maximum. I can't understand this, but I tried to move the upload/download rates around a little bit, to verify the finding: that I just should NEVER set the rates to infinite, and that (at least in ktorrent) the max download rate really was attainable. I haven't any idea why this worked for me, only that it did do this, reliably. I may go back to trying previous torrent clients now. What a fine way to spend the afternoon! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmXKZgACgkQz62J6PPcoOn0jACfe1wnh+JFmhQYi2UgjYRIc/y2 SFQAn2y5qjyzL3rEfmT8YOtq2MMuoKTx =xcN8 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
On Fri, 13 Feb 2009 16:21:32 +0300, Nikolay Tychina wrote: > Hello, > > i installed ktorrent3 and it seems to be very slow while checking pieces. > (~2mb per second) > (Deluge do it much more faster, i didn't try any other clients though) > Do you have the same problem? Do you mean 'Check data' for downloaded files? It gives me about 20Mb/s Max ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: ktorrent-3.1.6_1
Nikolay Tychina wrote: > Hello, > > i installed ktorrent3 and it seems to be very slow while checking pieces. > (~2mb per second) > (Deluge do it much more faster, i didn't try any other clients though) > Do you have the same problem? Same issue here. I get ~4MB/s or so. I started digging around and found that according to gstat (output at end) ktorrent is writing 50-60MB/s to ad18, which is my boot drive, sustained. Most of the other drives in the system are completely idle and belong to the ZFS pool the torrent data is actually on. I've checked using fstat and lsof and nothing leaps out at me. I also watched disk and swap space usage during the check and see nothing changing despite the apparent massive write load. I even tried doing a ktrace + kdump and searching for "write" but didn't find anything there either. I don't claim to be any expert with any of those tools though. Does anyone have any ideas on what to look at next? Thanks, Jonathan dT: 1.035s w: 1.000s L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name 0 0 0 00.0 0 00.00.0| ad8 0 0 0 00.0 0 00.00.0| ad8s1 0 34 0 00.0 32 430.55.1| ad16 0 0 0 00.0 0 00.00.0| ad8s1a 0 0 0 00.0 0 00.00.0| ad8s1c 0 0 0 00.0 0 00.00.0| acd0 1 3684 0 00.0 3684 589210.2 81.8| ad18 1 3684 0 00.0 3684 589210.2 83.2| ad18s1 0 36 0 00.0 34 392.19.2| ad10 0 29 0 00.0 27 331.17.9| ad12 0 34 0 00.0 32 430.45.5| ad14 1 3684 0 00.0 3684 589210.2 85.8| ad18s1a 0 0 0 00.0 0 00.00.0| ad18s1b 0 0 0 00.0 0 00.00.0| ad18s1c 0 34 0 00.0 33 833.06.0| da0 0 0 0 00.0 0 00.00.0| ad20 0 37 0 00.0 36 783.46.9| da1 0 36 0 00.0 35 832.35.9| da2 0 41 0 00.0 40 693.47.6| da3 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
