I'm sorry, but it has become unacceptable for me. KTorrent has to be the worst CPU hogger out there. I keep reading in the changelog about improvements to this, but all I see is **** after a ****, release in and release out... One can't even pull 5-6 torrents at a time without it trashing the CPU like a pig and as a result the whole system gets to a crawl. Repeat exact same procedure in another client, and I will bet my $$$ it'll do much better than KTorrent. The only nice thing for KTorrent going is it's well layed out GUI (the best out so far I've seen). But considering its performance, sorry to say it that no shiny GUI will make me stick to it when it acts like a pig all the time (and it's not even the fastest client out there anyways).

Yayyy for **** on CPUs! Nice job






So that's it. So long and thanks for all the hogging

</rant>

I had some problems with torrent corruption a while ago and George mentioned that I have over 100 running torrents.

Right now, I'm running about 150 torrents. htop consistently shows 8% CPU usage (6%+2%) across two processes. I'm not in a position to make specific comments on KTorrent efficiency but it's not a hog, at the very least. At least, it isn't a hog here the way I'm using it.


Here is my system:

AMD 9850
Foxconn A7DA-S (790GX/SB750)
8GB RAM
4 x 750GB Samsung F1 HDD
6 x 1.5TB Seagate HDD
8 x 2TB Western Digital
1 x 64GB Kingston SSDNow V+ SNVP325S264GB:
x86 Arch + KDE v4.5.1