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.
