Print

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

[skolnick]

Hi all!

I've been happily using my solaris computer with amule. So far, no crashes at all. I just compiled CVS from March 10 2005, it worked right, as expected. But after 24 hours of running, memory usage was 188MB, and it brought the computer to a whole crawl (190MB physical RAM, 300MB swap). Only two downloads in progress, and three completed files. Nothing that could produce such a high memory usage. Only thing was, the two downloading files stopped due to lack of free space, but that should be normal, so only uploading, no downloads at all.

Another interesting bug/feature I found is that, when downloading, if amule starts downloading the last chunk of the file, it won't allocate the full file space on the hard disk like emule does, but only the effective used space, which led me to believe I had more free space, and therefore the stopping of the downloads. Is this a solaris issue, aMule issue, or is by design?

Thanks.

[Xaignar]

Ok, the high memory usage is odd and will have to be investigated. As for the fact that aMule uses sparse allocation is known, it's simply because no-one has implemented pre-allocation in aMule. Is there any specific need for this? The only thing I could imagine would be to reduce fragmention, but beyond that I can't see any need.

[skolnick]

Originally posted by Xaignar
Ok, the high memory usage is odd and will have to be investigated. As for the fact that aMule uses sparse allocation is known, it's simply because no-one has implemented pre-allocation in aMule. Is there any specific need for this? The only thing I could imagine would be to reduce fragmention, but beyond that I can't see any need.

In my case, I think it is needed, since my hard drive is always almost-full, so allocating the whole filesize at once, prevents my downloads to become suddenly stopped. It could be an option, like emule does, but AFAIK, emule only implem,ents sparse files on NTFS (no idea why) so allocating full space is the default behavior.

Thanks.

[Xaignar]

That's because FAT32 doesn't support sparse files, only NTFS does.

[skolnick]

So that's why I never saw that effect on my current computer, because of FAT32 on my incoming/temp folders, but the solaris machine saves to a UFS filesystem, which *should* support sparse files, since I've seen this effect there...intresting

Thanks for the explanation...and if possible, adding the togge switch for this option would be cool.

[Kry]

The switch is there. The functionality is not

[skolnick]

Hmm...Ok, so the switch is no problem. I would even trade it for a really nice entry in the statistics tree telling me:
- Space available
- Space still nedded for my downloads to grow
- Space I need to free (if any)
Just like emule's!

Regards.

[Arichy]

Originally posted by Xaignar
Ok, the high memory usage is odd and will have to be investigated.

Same problem with too high memory usage:

I hav a pentium mmx, with 166 MHz and 92 MB RAM.
Running debian sarge with only vncserver and therein amule-cvs-20050816
(no other special applications or services)

After starting starting in the first 24h, memory usage is constantly 52 MB of 92 MB RAM and 4 MB of 98 MB swap.

But after some (e.g. four) days, RAM is over 90% and swap usage is 50%.

Then the computer gets slow and finally vncserver and/or amule crashes.

Sometimes there are mem alloc failures in syslog, sometimes there are no failures logged.
Last time, vncserver just exited, with amule still running as a process (but i needed to kill it either, because there was no display anymore).

[Mr Faber]

Try amuled, it is amule without a gui so it doesn't consume as much memory and cpu. You can manage amuled through amulecmd, a small console, amuleweb, a webinterface, and the remote gui which looks equal to normal aMule but some functions still aren't integrated.
By the way vnc isn't needed anymore .

cu
Mr Faber

[Arichy]

Originally posted by Mr Faber
Try amuled...

I am happy with monolithic amule in vncserver, I do not want to use something different.

Problem is not the memory or cpu usage, but the increasing memory usage (there seems to be a memory leak, as written in another thread)

[thedude0001]

Which GTK version does your wxGTK use? There's a logline at amule startup like this:

Code: [Select]

2005-08-24 05:46:01:  - This is aMule CVS using wxGTK1 v2.6.1 (Snapshot: r5326) based on eMule.
Please paste it here.

[Arichy]

Originally posted by thedude0001
Which GTK version does your wxGTK use?
Please paste it here.

Code: [Select]

Dies ist aMule CVS using wxGTK1 v2.6.1 (Snapshot: Tue Aug 16 07:02:05 CEST 2005), basierend auf eMule.

[Arichy]

aMule was killed again due to memory problems, it seems, after running 36h.

Here the /var/log/messages:

Code: [Select]

Sep  9 02:26:41 localhost -- MARK --
Sep  9 02:33:46 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:33:46 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:33:46 localhost kernel: VM: killing process addr2line
Sep  9 02:33:46 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Sep  9 02:33:46 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:33:46 localhost last message repeated 2 times
Sep  9 02:33:46 localhost kernel: VM: killing process xfce4-panel
Sep  9 02:33:46 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:33:46 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Sep  9 02:33:51 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:33:51 localhost last message repeated 3 times
Sep  9 02:33:51 localhost kernel: VM: killing process addr2line
Sep  9 02:33:53 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:33:56 localhost last message repeated 2 times
Sep  9 02:33:56 localhost kernel: VM: killing process addr2line
Sep  9 02:33:56 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:34:00 localhost last message repeated 6 times
Sep  9 02:34:00 localhost kernel: VM: killing process addr2line
Sep  9 02:34:00 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:34:00 localhost kernel: VM: killing process addr2line
Sep  9 02:34:00 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Sep  9 02:34:13 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:34:13 localhost last message repeated 2 times
Sep  9 02:34:13 localhost kernel: VM: killing process amule
Sep  9 02:34:14 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:34:16 localhost last message repeated 4 times
Sep  9 02:34:16 localhost kernel: VM: killing process Xrealvnc
Sep  9 02:34:16 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:34:16 localhost kernel: VM: killing process addr2line
Sep  9 02:34:16 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep  9 02:34:16 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Sep  9 02:46:42 localhost -- MARK --
Sep  9 03:06:42 localhost -- MARK --

This problem limits the usability of amule very much, a solution would be very nice...

[stefanero]

restart it!?
as long as we dont find the memleak I see no other option then restart amule every 24-36h maybe...
I know its not the sollution you want but as long as we dont find the memleaks I see no other way atm.
 
you could try amuled which is much better with mem, but if you dont want to....

[Kry]

Try with wxCVS