aMule Forum
English => en_Bugs => Topic started by: kristof on April 30, 2011, 11:26:51 PM
-
aMule 2.3.1rc1 normally uses 10-15% cpu on my dualcore Intel e5200. However, sometimes cpu use jumps to 160% (100 of one core and 60 of the other core). aMule continues to run normally under such condition but does not return to normal cpu use even after one hour or more. Once cpu use is high it remains high.
GUI interaction is slow but works. Download speed remains good. Files correctly complete when they are finished downloading. The only effect seen other than slow gui is incorrect download speed.
This might be related to the wx socket problem discussed here http://forum.amule.org/index.php?topic=18822.0 but one cannot be sure. After some time aMule will crash due to the wx socket bug but it can be many hours if the number of downloads is kept small.
Ubuntu Maverick, aMule 2.3.1rc1 debug / no optimize, wx 2.8.12 debug / no optimize
What diagnostics can I provide for this?
-
aMule has made a liar out of me. I have just observed a return to normal cpu use after a period of high cpu. High cpu lasted roughly one hour.
I should add that aMule is always the only application running on this machine. e5200 with 2gb ram. 1tb disk with filesystem 8% full.
One file may have completed during this time but it is possible that it had completed before high cpu began.
-
I always run with optimize on. Without optimizations some task will take a lot of CPU. Note that using debug and optimize together is possible.
-
10-15% cpu I gave was incorrect for debug + no optimize. They are my no debug + optimize numbers. With debug + no optimize I see cpu use of 23-30%. Since this machine runs only amule I don't mind using 30% if I have a better chance to help diagnose the wx socket bug.
The cpu use that I find unacceptable is the 160% number. It seems unreasonable for a somewhat speedy dual core processor. Something must be wrong to see such high cpu for periods of one hour or more.
My first priority is finding the maximum connection count setting that triggers the wx socket bug. However, I am also keeping a close watch on cpu use. I have seen extended periods of high cpu three times since yesterday. I am wondering if "rogue clients" could be the cause. I plan to enable an ipfilter during a period of high cpu use to see if there is an immediate positive effect. I have not yet been able to observe a time of high cpu use since I had the idea.
I read on the emule boards that people have seen kad abuse originating from some ip blocks. It is only luck if the cause of my high cpu is because of rogue actors and that their ips might be inside my ipfilter list.
-
I enabled ipfilter during a period of high cpu use but there was no effect.
-
How many files are you sharing?