Anyone seeing very large cpu usage in late svn builds?

Where I have 1-2% max on 2.0.2 I get 20-30% (sometimes as high as 90%) with my svn build.

Yep same here...
I'm running on a little 800MHz C3 Epia, and I had a steady 50% cpu graph running 2.0.2.
Yesterday's svn version peaks to 100% quite often.

But more concerning... Download througputs are not as high as 2.0.2.
I get about a 1:1 ratio.

In 2.0.2 that is about 3:1 or even higher.
I've switched a couple of times, and this was the case every time.

Edit:
Above statements still valid,
But..
I don't want to just complain on what is only my second post.
To the writers of this great peace of work: thanks, kTorrent rocks.
(I came from Azureus myself)
If you guys can pull it off to prevent kTorrent from being a cpu-hog (since i'm running it on a little C3) i'll never use anything else

Cheers, Tony

I wouldn't say it's complaining when posting about svn builds , more notifying the developers that there are some issues there.

(I waited with posting until it'd been there a few days, to see if it was a temporary thing in the svn tree).

Anybody know when this started showing up ?

George wrote:Anybody know when this started showing up ?

I only switched to ktorrent fairly recently. If you have some svn revisions you want tested I can do that though.

You can use the weekly snapshots to test this :

http://ktorrent.org/downloads/svn-snapshots/

I will do some profiling tomorrow or the day after that.

George any updates? I don't have the chance to get this tested right now, as the monitor on that computer died on me.

Not yet, I will get started on this later this evening.

this is gonna be one of those fun bugs....

I just compiled ktorrent with profiling support and now it's fast as lightning.

Without profiling support it's slow as hell, the entire gui seems to "lag", and there's a delay on opening dialogs and such.

flags with problems:

Code: Select all

CFLAGS="-O2 -march=athlon64 -msse3 -pipe"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common -Wl,--hash-style=both"


flags with no problems:

Code: Select all

FEATURES="nostrip"
CFLAGS="-O2 -march=athlon64 -msse3 -pipe -g -pg" CXXFLAGS="${CFLAGS} -g -pg"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common -Wl,--hash-style=both"


note that features="nostrip" is a gentoo thing, it per default strips debug information from binaries. That disables it.

neuron wrote:this is gonna be one of those fun bugs....

I just compiled ktorrent with profiling support and now it's fast as lightning.

Without profiling support it's slow as hell, the entire gui seems to "lag", and there's a delay on opening dialogs and such.

flags with problems:

Code: Select all

CFLAGS="-O2 -march=athlon64 -msse3 -pipe"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common -Wl,--hash-style=both"


flags with no problems:

Code: Select all

FEATURES="nostrip"
CFLAGS="-O2 -march=athlon64 -msse3 -pipe -g -pg" CXXFLAGS="${CFLAGS} -g -pg"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common -Wl,--hash-style=both"


note that features="nostrip" is a gentoo thing, it per default strips debug information from binaries. That disables it.

What the hell, let me try compiling with the same flags, see if I get the same results.

I'm seeing some higher then expected CPU usage with these flags.

updating to latest svn and it seems a LOT faster, don't know exactly what revision fixed it (guessing one of the commits to change how CXXFLAGS/LDFLAGS are dealt with?). In either case, thumbs up

neuron wrote:updating to latest svn and it seems a LOT faster, don't know exactly what revision fixed it (guessing one of the commits to change how CXXFLAGS/LDFLAGS are dealt with?). In either case, thumbs up

It is still using more then it used to be using, I'm gonna do some manual profiling (gprof + amd64 + shared libraries is not a good combination), to see if I can find some performance hogs.

George wrote:

neuron wrote:updating to latest svn and it seems a LOT faster, don't know exactly what revision fixed it (guessing one of the commits to change how CXXFLAGS/LDFLAGS are dealt with?). In either case, thumbs up

It is still using more then it used to be using, I'm gonna do some manual profiling (gprof + amd64 + shared libraries is not a good combination), to see if I can find some performance hogs.

I've done some testing myself, not with a profiler (because I can't get it to run slowly with profiler flags cflags).

When I started it up, it ran really smooth, but uploading I'm seing huge cpu usage. I get a feeling I could download fast, but uploading used a ton of cpu usage.

(uploading at around 600kb/sec on a random torrent I was seing cpu usage of around 30%, when downloading a torrent I had a cpu usage of around 2%).

It all seems fairly random though, so it's a guess at best.