[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mldonkey-users] Memory consumption
From: |
MLdonkey |
Subject: |
Re: [Mldonkey-users] Memory consumption |
Date: |
Mon, 27 Jan 2003 13:47:58 +0100 |
> Hi there,
>
> First off, a big "thank you" goes out to all the mld developers! Great
> work!
>
> I upgraded to mld 2.02-7 from cvs today, and so far it's running
> smoothly. The only thing that worries me is the enormous amount of
> memory that the mldonkey process uses - right now it's about 230 MB! I
> remember some people on this list had a mem usage of about 80 megs...
> Which is imho a lot but would still be acceptable...
>
> There was an older version (think it was 2.00+pangosomething) that used
> only 17 megs of memory - while the download rates were still quite ok.
>
> My mldonkey runs on a redhat 7.2 box, kernel 2.4.7, ocaml 3.06. I am
> d/ling 11 files right now, some of them very rare.
The memory usage of mldonkey has always been a problem. We are
currently trying to debug this (the 'mem_stats' command will display
more information). In the meantime, we REALLY need more information on
what you have done to get such a memory usage. Can you reply to these
questions (and other on the list too if they have the same problem):
- Does mldonkey start with this memory usage, or does it increase
slowly ?
- What do you do with mldonkey ?
* which plugins do you use
* which kind of interactions do you have with mldonkey before it goes
to that amount of memory:
- which interface do you use (gui, www, mldonkeywatch, telnet..)
* do you use it a lot ?
* do you reconnect often with the gui ?
- how many files are you downloading
- how many sources do you have ('sources' command)
- what does 'mem_stats' say (only the last lines)
- have you tried some searches ? do you have some friends (with
listed files ?) do you use the results history ?
- is it increasing even without interaction ?
These informations can lead us to understand where the memory leak is
coming from, before printing more debugging information ?
- MLDonkey