Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[setrone]

aMule 2.1 and 2.2 work VERY SLOWLY in may computer (

[wuischke]

Welcome setrone!

Do you mean that the download is very slow or do you mean that aMule works very slow?
In the second case: What's your hardware?

paka!

[setrone]

aMule works very slow
iMac G5, 1.8G, 768 DDR, xDSL connection 256/128, Wi-Fi adapter D-link.
No problem with connection. No problem with speed downloads.

Sorry. Mac OC X 10.4.6

aMule-Mac.CVS.2006-01-14.Debug - ok  :-)

[wuischke]

OK, do you know how much % of the CPU is used by aMule?

BTW: I included all information in one post. You can easily edit you post by clicking on the -button.

[lionel77]

Hi setrone-

we've been struggling with aMule's CPU hungriness for a while now (primarily on Mac OS X). If I remember correctly, the whole thing started some time after 2.0.3. Ken and I have put a lot of work into trying to figure out what the cause of aMule's resource hunger is, using profiling tools such as Shark, but to no avail so far.
Usually, it takes a few hours until aMule max'es out the CPU and becomes slow. The main factor seems to be (as far as I can tell) the number of popular files you download.

One reason why the aMule-Mac.CVS.2006-01-14.Debug version may run a little better on your machine than the 2.1.2 version could be a modification I made to the core timer (I set it to 500ms instead of 100ms). On my machine that does not seem to fix the issue but it seems to postpone it a bit. I think, I will from now on build the release binaries with a slower core timer interval, too.

One thing you can do to reduce aMule's CPU usage a bit is to switch to a window that does not get updated frequently, like the messages or the search window. Whenever I'm not interacting with aMule, I switch to one of these windows and then hide aMule.