Print

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

[DCTapeworm]

Hi there,

(please delete or move if redundant with a similiar thread (or should be recategorized).

I'm not sure if this helps, but I was previously using aMule 2.1.1, and experiencing the SAME application slowness (i.e the rainbow spinning disk) that's going on in aMule 2.1.3.

The app slowness happens no matter if I'm connected via wireless access or not through my Powerbook.  

I used to use aMule 2.1.1 without apparent problems for quite some time.  Just started it up last week and sllloooowwww...

Tiger OSX and 1GB of RAM.  Any other info I'll be glad to post.

[lionel77]

Here's an earlier reply of mine about aMule's slowness:

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 couple hours or even a day 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.

So until this is fixed, you might want to download only a smaller number of popular files at the same time and restart aMule when the sluggishness gets too bad.

EDIT:
Oh, almost forgot, it also helps to switch to one of the windows that does not get updated (e.g., the friends window) and hide aMule, when you don't use it.

[DCTapeworm]

Hi Lionel77,

Yah, I caught that thread, but my experience is that aMule slows within 2 seconds of connecting to a server.  I have full connect, green arrow, no files being downloaded, and throttled upload at 21k.  

When offline, exact same thing.  Trying to change anything in the configuration menu just causes the rainbow spinning disc to start.  aMule is the only thing running (beyond Dashboard).

So, in contrast with the referenced reply, mine is pre-file download and pre-net connection.  
Anything I could try or monitor to provide some helpful info?

All the same, I hope the aMule crew figures this out.

[chowder]

i just found out about this app looking for an alternative to bittorrent, but i'm also seeing intensive resource use. it's almost as bad a azureus. this project is c++, i was hoping it would be similary quick as transmission bittorrent client.  i even compiled it myself to see if that would help, but it didn't.

[lionel77]

In terms of resource usage, amuled (the core-only version of aMule) has a much smaller footprint than aMule monolithic (the regular stand alone version). Unfortunately, amuled is still pretty unstable on OS X, because on OS X we have focussed or energies primarily on the monolithic version so far. We are, however, in the process now, of trying to get amuled to run decently on OS X as well, so that users of older machines will have a client that works reasonably well on their machines.


@DCTapeworm:
Have you tried varying the number of files that you download and share to see if that has an effect?

[DCTapeworm]

Hi Lionel,

Unfortunately that hasn't had much of an effect.  Just getting to the search screen involves click, wait 20 seconds, type in search, wait 64 seconds for the letters to appear in the search box, and then clicking the search button locks me into the spinning wheel mode.

Machine is a Powerbook G4 with gig of ram.

I'll tool around with it some more when I'm back from work this evening.  I'll try allocating some more resources to it to see if that makes any difference.