aMule Forum

English => en_Bugs => Topic started by: Lenni on May 02, 2005, 05:24:57 PM

Title: 20050430 using up all cpu resources
Post by: Lenni on May 02, 2005, 05:24:57 PM
Hi!
I'm having some problems because my amuled is using up all remaining cpu resources after a few minutes of running.
I'm currently running CVS 20050430 compiled using wxGTK 2.6 on a Celeron 400 (or something). The last version I used (CVS 20050408) used to use only 20-50%. I hope you can help me by fixing this.
Thanks in advance!
Lenni
Title: Re: 20050430 using up all cpu resources
Post by: stefanero on May 02, 2005, 05:38:22 PM
well try tomorrows,
kry changed something in the way the stats for dl/up files get saved, so if you have a lot of files every 60sec you have really high CPU peak, will be fixed tomorrow...
Title: Re: 20050430 using up all cpu resources
Post by: Lenni on May 03, 2005, 05:22:50 PM
Hi!
Did you mean 2.0.0 or CVS20050503, 'cause 2.0.0 didn't fix my problem  :(
Lenni
Title: Re: 20050430 using up all cpu resources
Post by: stefanero on May 03, 2005, 05:40:21 PM
didnt? should be fixed in both...
Title: Re: 20050430 using up all cpu resources
Post by: Lenni on May 13, 2005, 04:09:36 PM
Hi again!
I'm using CVS20050510 now and am still having the problem.
Plus amuled does not find any sources for newly added files after running for some time.
When I exit amuled it produces a core-file, which I will post in the Backtrace-Forum (http://forum.amule.org/thread.php?threadid=6151&sid=).
Please help me, everything is so slow  ;(
Lenni
Title: Re: 20050430 using up all cpu resources
Post by: stefanero on May 13, 2005, 04:43:02 PM
do you have a date where the problme is NOT? have you tryed 2.0 final?
is the "slow" problem and the no sources problem in that version aswell?
Title: Re: 20050430 using up all cpu resources
Post by: Lenni on May 13, 2005, 05:08:26 PM
I tried 2.0 final, but It was the same without the source-problem. The last version running fine was something in the beginning of april, if I remember correctly.
Is it possible, that it has something to do with the newer versions of wxGTK?
Title: Re: 20050430 using up all cpu resources
Post by: stefanero on May 13, 2005, 05:13:18 PM
well 11th.04.2005 is atm the last tarball availible, can you try this one? so we have a starting point for debug?
and really try it with wx-2.6 so the amule-cvs version is the only difference. and I see if I can get a tarball from 01.04.2005 for ya, if this is ok.

stefanero
Title: Re: 20050430 using up all cpu resources
Post by: Lenni on May 13, 2005, 05:40:01 PM
That's the point, it is possible, that the I comiled the last "fine running" version with wxGTX 2.5.something and the newer ones with wxGTK 2.6.
I'll get the tarball from the 11th and will compile it.
Thanks for your time.
Lenni
edit: the last fine version here was cvs20050408 (see first post)
Title: Re: 20050430 using up all cpu resources
Post by: stefanero on May 13, 2005, 05:49:09 PM
well huh?

stick to wxGTK-2.6 something and check if the cvs20050408 tarball for example, still works or not.

so in the end we know its either wx or amule ....
Title: Re: 20050430 using up all cpu resources
Post by: Lenni on May 19, 2005, 08:42:48 AM
Hi!
After a some testing with several tarballs, and installing a whole new system onto my pc (I had time over the weekend), I finally found out, that it is wxGTK2.6 wich causes the problem here. Even 2.0.1 with wx2.6 used up all resources.
Finally using 2.0.1 with wxGTK2.5.4 fixed my problem.
I hope I didn't waste your time too much, thanks for your help!
Lenni (now on gentoo)
Title: Re: 20050430 using up all cpu resources
Post by: deltaHF on May 19, 2005, 11:47:06 AM
deltaHF  14380 11.2 10.7  60028 41504 pts/0    S+   May18  94:07 amule


wxgtk-2.6.0 + amule-2.0.1
Title: Re: 20050430 using up all cpu resources
Post by: darklegion on May 19, 2005, 01:57:47 PM
Are you using any optimized CFLAGS? Both wxgtk and amule seem to be very sensitive to anything but the most conservative,such as just -O2 and -fomit-frame-pointer.I don't use gentoo but I know you can set specific CFLAGS on a package basis,so you might want to do that(assuming you are using optimized CFLAGS)