aMule : makes computer hang after a few hours ??

[Colin Brace]

On 12/21/05, Vincent Trouilliez <vincent.trouilliez at modulonet.fr> wrote:

> I really didn't think that managing 500+ files would cause that much CPU
> load on a 1.5GHz CPU.

I am sharing more than that and performance has not been an issue.
Note that *sharing* files is less system-intensive than *downloading*
them, hence my advice above to limit the number of active downloads.

> The other problem is that the aMule keeps
> UPloading stuff to other people (fair enough for P2P s/w ;-), and this
> eats all my (limited to only 128kpbs) upstream bandwidth, which keeps
> internet and Synaptic from working properly/fast, regardless of how much
> downstream B/W is actually available. I tried to reduce the upstream B/W
> limit in the aMule preferences but it doesn't seem to take effect.

This is not the right forum getting aMule support, but let me explain
this to you since it is confusing: in the preferences notebook, there
are four relevant entries to fill in (I am not sure the exact
wording):

  Bandwidth limits UP
  Bandwidth limits DOWN
  Speed limits UP
  Speed limits DOWN

This first two pertain to your total bandwidth available. In your case
it will be 128k UP and whatever (1Mb?) down.

The second two constrain the amount of bandwidth you wish to dedicate
to aMule. As a general rule of thumb, don't dedicate more than 80% as
this chokes latency. In your case, I would dedicate 100k up and half
(500K or whatever) of your download capacity. Once you have entered
the correct settings and closed Preferences, aMule will  immediately
start respecting your bandwidth limitations.

FYI: aMule uses your total bandwidth settings for generating graphs,
no more (see the Statistics page).

> I though that plenty of RAM was enough for P2P, but looks like
> processing power is also on order then.

No, your current system will run aMule just fine; as I said above,
just don't overdo it on the downloads. Have patience!