mldonkey-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mldonkey-users] [CVS 2.02-4] eating up all RAM and doing nothi


From: Roland Arendes
Subject: Re: [Mldonkey-users] [CVS 2.02-4] eating up all RAM and doing nothing
Date: Tue, 14 Jan 2003 16:07:35 +0100 (CET)

Hi

>>  In 2.02-4 there seems to be no way that file_sources.ini can shrink.
>> After
>>  every restart it gets bigger and bigger. So I think the only solution
>> for
>>  2.02-4 is to delete the 2 files on startup (just like this servers*).
> Could you verify some things in these --big-- files: is the same source
listed several times ?
> grep source_addr file_sources.ini | sort | uniq -d
> or something like that...

-rw-r--r--    1 donkey   donkey   49895997 2003-01-14 12:23 file_sources.ini

address@hidden:~/build> grep source_addr file_sources.ini | sort | uniq -d
| wc -l
  11482

address@hidden:~/build> grep source_addr file_sources.ini | sort | uniq |
wc -l
 237719


address@hidden:~/build> grep source_addr file_sources.ini | sort |  wc -l
 249262

> Can one source have several times the md4 associated in its
> source_files ?

Looks like about 5% are several times associated.

>>  PS: There is still no fix for the incrementing-Port-Server- and the
4662-Server-Flood. :-(
> incrementing-Port-Server-: what's that problem ? I missed something...

Some days ago I sent you a mail personally and to the list (size of 240k).
The mail to the list got stuck because it was too large, but you should
have received it. It was a part of my serverlist, and if you have a look
at it, you'll see what I mean.

Its a serverlist of mine (after 10 minutes of uptime) which consists 99%
of 4662-servers and ONE IP with about 20000 different ports (the
serverlist had about 22000 entries).

I can send it again to you, if you want. I have 6 other guys with the same
problems (they're not on this list).

Roland

PS: Because of save_options_delay defaults to 240, a large impact on
up/downloading (complete stall of traffic) every 4 minutes can be seen
using ifmonitor, because mldonkey needs some time (about 2 minutes) to
write the whole 50MB file to disc. This improved greatly after changing
save_options_delay to 1800.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]