aMule Forum
English => en_Bugs => Topic started by: Mjoker on January 12, 2006, 05:07:27 PM
-
Hi there,
I look thorugh Forum for some info about this particular case that may be similar to mine but I didn't came across any explanation or advise [probably I overlooked something, in that case, I'm sorry and I'll be glad for guidance]
I've used aMule 2.1.0 since yesterday and I've noticed that it takes much more of my CPU than version 2.0.3.
I made apt-upgrade at my Debian Testing which upgraded aMule as well. I didn't change anything in aMule settings and just started program. I noticed that while 2.1.0 is running it takes about 30-40 % of my CPU all the time whereas previous version of program took only 3-5% max.
I thought that reason might be in hashing process or in crazy famd which sometimes steal much of my CPU, but no. Everything was hashed and I killed famd and CPU usage was still about 30-40%.
Then I started to make some changes in aMule's settings and turned off some things that I thought may be taking CPU, but it didn't help at all so I returned to my old ones [like it was in previous version].
At the moment aMule is running and as my System Monitor tells me that 30% pf CPU is taken by aMule and it doesn't seem to drop. It also strange because this CPU's usage is irregular: it doesn't keep those 30% but jumps from 30 to 50 %. Previous version of aMule took 50% of CPU whet it started, then again 50% while it was connecting to server and then it dropped to safe 3-5% and took more only when was completing downloaded file.
Now, with 2.1.0 I have to pay much much more attention to CPU' usage and have problems with using other programs while aMule is running - for. ex. if I open any other application, CPU's usage jumps even to 100%; but when aMule is off, nothig like that happens and I can have several programs open and used without any strange events.
Is it some kind of bug? Or is it caused by some completely new functions of program that are implemented since previous version that I haven't noticed after using my old aMule's settings? Where should I look for reason?
I would like to see 2.1.0 running just as previous one: without stress, eating of CPU and on the other hand - with possibility to convenient use of other application as well. Especially because aMule runs all the time I use my computer, sometimes even days/weeks without a break and such CPU's usage can be real pain.
BTW: Sorry for my English... I know it's kinda rough and dusty.
Edit: I add that my CPU is Pentium IV 2.6 Hypertherading.
-
The most significant change in 2.1.0 that might cause increased CPU usage is Kad. Try disabling Kad and see if that affects your CPU usage.
-
Originally posted by ken
The most significant change in 2.1.0 that might cause increased CPU usage is Kad. Try disabling Kad and see if that affects your CPU usage.
Hi, big thanks for reply.
I tried this, I checked settings and I have Kad off because I do not use it [I cannot use it for some reasons connected with my network].
Anyway, Kad being off doesn't help. I still have min. 30%, but sometimes even 60-70% of CPU taken by aMule 2.1.0.
What is worst is that it's all kinda erratic and irregular. I mean those jumps from 40% to even 80-90% at the time. Program takes sometimes even 100% of CPU and after it I got those messages about temperature over the threshold which is strange, because this is the only case when I got such messages.
At the moment I had to shut down aMule because it was impossible to have it running and using webbrowser at the same time and not get those messages in terminal. Weird, isnt'it? Especially considering two facts:
[1] I can use several quite big applications that aren't aMule and my CPU doesn't works at its 100%, it doesn't go even till its 50% and there's no indication that anything is over temperature threshold.
[2] Previous version of aMule usually took only 3-5% and I cannot recall any events when CPU was taken so much buy this program without any logical reason.
-
I have the same problem here.
at the moment amule takes 60-70% CPU usage. That is on a AMD XP 2000+ with 1GB ram far to mutch for amule (without any special actions running like complet files or calculate new hash)!
cu
Fossybaer
-
Compile yourself and retry. We give no support for precompiled packages, sorry :)