I am using ktorrent since version 1.2-20, and am very glad to watch its developement lately; version 2.0.3-1 was a big step forward, and so I was pretty eager to try the 2.1 beta when reading about its new features - and talking about new features I am defenitely not disappointed. The new GUI is a major improvement, especially the abillity to shut a 'search'-tab is very useful since many torrent-sites are heavily loaded with animated advertisements which not only are annoying but in some cases even slowed down my system, so I always had to switch to a less cluttered site. Creating groups is useful, too. I have no idea about rss-feeds (never really used them) so maybe you could give an explanation on how to use this feature within ktorrent at all (for us rss-noobs). While I'm at it: why can't I find any manual for ktorrent?

Now, there are two bugs I recognized so far:

1st: When changing a groups name, the changes are not found when right-clicking on the torrent in the torrents-list and choosing 'add to group'. There the goups name stays the same.

2nd: Normally the beta takes about as much cpu as the 2.0.3-1 (between 3 and 15% on my sys, with an estimated average cpu-usage of maybe 6%), however, every about 10 or fifteen minutes it suddenly starts taking huge loads of cpu (up to 99% = whatever it can get) for about 15 seconds - in one case it even did so when all the running torrents were stopped. I'm not too sure whether this is a permanent phenomenon, but if so, I'll have to deinstall it soon and go back to the stable 2.0-version until the official 2.1 is out. Well, it's still a beta...

My sys: SuSE 10.1 on KDE 3.5.5 and I used the .rpm for (surprise!) SuSE 10.1

gropiuskalle wrote: While I'm at it: why can't I find any manual for ktorrent?

It's being worked on, we had planned to include something with the beta, but because of some unforseen circumstances it was decided to postpone this until the next release.

1st: When changing a groups name, the changes are not found when right-clicking on the torrent in the torrents-list and choosing 'add to group'. There the goups name stays the same.

It seems you are correct, there is something going wrong there.

2nd: Normally the beta takes about as much cpu as the 2.0.3-1 (between 3 and 15% on my sys, with an estimated average cpu-usage of maybe 6%), however, every about 10 or fifteen minutes it suddenly starts taking huge loads of cpu (up to 99% = whatever it can get) for about 15 seconds - in one case it even did so when all the running torrents were stopped. I'm not too sure whether this is a permanent phenomenon, but if so, I'll have to deinstall it soon and go back to the stable 2.0-version until the official 2.1 is out. Well, it's still a beta...

Well, that's not normal, does the same thing happen when you disable DHT ?

Well, that's not normal, does the same thing happen when you disable DHT ?

Yes it does.

Yet ktorrent changed its behavior a little (even before disabling it) - the intervals between the need of much cpu get longer and it lasts shorter - so while yesterday it happened every ten minutes for 10 to 15 seconds or so, it now won't happen for several hours and when it does, it's over after about three seconds or even less. I wish I could give you some more precise info about that, but it happens totally out of the blue and I can't see any connection to what I am doing and what cpu-needs ktorrent has. Sometimes it goes up while I am adjusting some settings in ktorrent, sometimes it happens while I'm doing nothing at all. Um...

Might there be some problem with the SuSE 10.1-.rpm? Because I am willing to compile the beta myself and build my own .rpm via checkinstall if you'd think there could be any difference.

Beside that, I also noticed that ktorrent 2.1 is much faster in downloading than any version before. Don't consider this info being part of the bug-report, please

I get about 6% cpu usage on an old athlon xp 2000+ @ stock. I haven't yet noticed any spikes you speak of. I wonder if its the option in advanced preferences "Do a data integrity check after _ corrupted chunks". I dont know if a corrupted chunk means it hasn't written to the HDD correctly or its received bad data from a client but if its bad data from a client than that may explain things as it can happen on a regular basis for some torrents.

nitehawk wrote:I get about 6% cpu usage on an old athlon xp 2000+ @ stock. I haven't yet noticed any spikes you speak of. I wonder if its the option in advanced preferences "Do a data integrity check after _ corrupted chunks". I dont know if a corrupted chunk means it hasn't written to the HDD correctly or its received bad data from a client but if its bad data from a client than that may explain things as it can happen on a regular basis for some torrents.

You will get to see a dialog when KT does the check and this is only done when corrupted chunks are detected after they are loaded from disk. If KT receives bad data, it will just discard it.