g wrote: > Patrick O'Callaghan wrote: > <snip> >> Frankly, that's not a convincing explanation. Torrents are almost >> entirely I/O bound, and this is a DSL connection rated at 2Mbps which in >> fact is less than that in practice. No way could a torrent client be >> eating 80% of a 64-bit Intel Core 2 Duo with 2GB of RAM. It's just not >> reasonable. > > i have dsl lite i=765kbps / o=133kbps. in having used both ktorrent in f8 and > ctorrent in sl5.2, both used up to 85% cpu. > > after watching graph in ktorrent, i disabled several sites that where being > checked but showed little to no action and disabled file access in, which > increased thru put from active sites. do not recall exact cpu change, but it > was worth it. > > with ctorrent, i again disabled file access which dropped cpu usage to below > 70%. > > have you tried setting nice? You have a problem with your ktorrent/ctorrent installations. I've run ktorrent on my Slackware box with several active torrents, and at most it took 6% of one CPU. See my other post about rtorrent, which takes 1% or less with many more torrents active. rtorrent is the client to use, but being CLI, you'll have to memorize some of the keyboard commands to utilize it fully. -- Jason Turning -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
