Follow-up Comment #13, bug #18959 (project mldonkey):
yes, i can confirm such behaviour. i'm on Debian testing @ 2.6.32 and using
version 3.0.2 (self-built), but also tried mldonkey-server 3.0.1 (from Debian
repos) - the same.
the problem is: i currently have about 17G shared. when i run mlnet without
any networks, all is fine. when i enable DC nework, all is fine again (i've
already hashed shares for DC). but when i connect to one hub - it begins to
eat about 15-20% of cpu. if i connect to 5 or more hubs - it eats all
available cpu and thus, of course, works sloooowly. it also eats some memory,
but there are no such critical amounts. at that time i'm only connected to
hubs, i do no searches/up/downloads/chat/anything. i've disabled
auto-rescanning, minimized number of open slots - no results
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?18959>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Mldonkey-bugs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/mldonkey-bugs
