Re: [Mldonkey-users] Re: mldonkey eating up all memory again

[René Gallati]

>> As I already wrote on this list and also made a comprehensive bug
>> report (Bug 1555 see here
>>
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1555&group_id=1409 )
>Ok. My files don't exceed 700 sources and I only connect using ISDN, so
>this seem both be the limiting parameters on my side.

Well 700 is several houndred sources. I cannot tell you if this suffices or
not to trigger the bug. You can see it yourself though. If mldonkey uses
more upstream bandwith than you set with hard_up_max, then it has already
happend.

Mldonkey does honor the upstream limit very closely as long as this bug does
not crop up. When it does, your upstream will be significantly (ok depending
on capacity) higher. In my case, upstream usage jumps from 5KBytes/sec to 14
(which incidentally is nearly the limit of the pipe)

>> the memory (and CPU and bandwith) eating behaviour on mldonkey ONLY
>> appears if you have a high-source file in your download list. A
>> high-source file is a file, where several houndreds of peers for that
>> file are known.
>Do you have a link which gets several hundreds/thousands of sources, so
>I can experience the bug myself?

I had though due to the nature of the net, I doubt there are still ~4000
sources around for the file. However, just head over to sharereactor.com and
wait until the new bond movie or new starktrek or new lotr movie is
released. That will instantly give you a "fresh" high source file for
certain. For comparison, it helps having mldonkey work for some days with no
high-source files and monitor the bandwith constantly, for example with mrtg
or rrdtool, it's impossible not to see the difference (have you had a look
at my statistic-picture I attached at the bug report? You'll see something
similar, I've done it on two entirely systems now.)

>> However it IS a bug in mldonkey, no matter what people are saying who
>> can't reproduce it, and unless it is fixed, consider cancelling all
>> files in your mldonkey which are high-source and then restart
>> mldonkey. At least it wont drive your box into the constantly swapping
>> mode.
>Since mldonkey v2 does not search for files which are paused, shouldn't
>pausing them be enough to stop the problem? Do you really need to purge
>them completely from the files.ini, as you suggest in your bug-report?

Pausing them did not help. I paused the file and had an hour later still too
much upstream. I suspect that is some kind of backlog and eventually it
*would* have died down. However it simply got "too much" and pausing and
then restarting mldonkey helps instantly. You don't need to remove the file
if you don't want, but just pausing won't do the trick immediatly. However
pausing the file(s) then killing the core and restarting will immediatly
help.

I also watched the traffic with a traffic sniffer (etheral to be exact) and
I saw that all what mldonkey did, was contacting houndres of peers and
asking them for the file slot or chunk list (tcp-connection, packets had
sizes ranging from 15 to 60 bytes) and this continously to houndreds of
peers. I also had over 400 connections open, most of them were useless at
that time because mldonkey literally chokes the pipe to death.

--

C U

     - -- ---- ----- -----/\/  René Gallati  \/\---- ----- --- -- -