Registered Member
|
KTorrent is currently using up 50%+ cpu, and its being rather uninteractive at the moment.
I hooked up gdb to the running ktorrent, and it seems to be in QGList::findRef most of the time. I shall build a profile build soon to see if thats true. |
Moderator
|
|
Registered Member
|
|
Registered Member
|
|
Moderator
|
It should be OK, except for to high CPU usage when connections authentications are going on (doesn't happen allways, which makes this a bit weird). Most of the time it should be OK. |
Moderator
|
|
Registered Member
|
Unfortunately last night I found ktorrent using 99% CPU, and I wasn't home to do much about it besides kill it from ssh. If it happens again, I'll attempt to debug it.
edit: Say I have 20 torrents going (and 20+ more queued), and 40+ connections per torrent, how much CPU usage should I be expecting? (60%+ ?).. I'm doing a svn up (right now, as I edit) and a make distclean, to start with a fresh proper build, see if some faulty dependency tracking caused some of my problems. edit2, oops, it seems I had it set to 150 connections per download. But bumping it down to 40, didn't make any difference, even after a restart of ktorrent. |
Registered Member
|
|
Moderator
|
|
Registered Member
|
Yes EDIT: After turn off the protocol encryption, it looks that the CPU usage is back to normal. It looks looks like a bug in the Protocol encryption. Im wondering why the protocol encrytion works only with µtorrent clients and not with Azureus clients ?!? |
Moderator
|
Euhm, to implement the encryption, I used Azureus as my test platform, so this should work. I will do a check if the new socket code hasn't broken this for some reason. I think I know where the problem lies with the 99 % CPU usage. |
Moderator
|
|
Registered Member
|
|
Moderator
|
|
Registered Member
|
I tryed it again with the latest svn version, but it is always sthe same wit the cpu load.
-with encryption on, ktorrent use all the time 99% of CPU power -with encryption off, ktorrent use all few minutes 99% CPU power, but only for around 20-30 sec. than it will go back to normal ...
Last edited by LinuxDoc on Sun Jul 02, 2006 10:00 pm, edited 1 time in total.
|
Registered users: Bing [Bot], Evergrowing, Google [Bot]