-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? - -- tc,hago. g . in a free world without fences, who needs gates. learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html.gz 'The Linux Documentation Project' http://www.tldp.org/ 'HowtoForge' http://howtoforge.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFI8jur+C4Bj9Rkw/wRAmeKAKDW+Zdpbe+Ar3l9NoVz4/xj3P8z2QCgyoUf ZmDRHL7Nqsa7h4+m6EvS57g= =eiuC -----END PGP SIGNATURE----- -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
