[Mldonkey-bugs] [bugs #3761] FT not respecting max sources per file settings

[spiralvoice]

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a free e-Donkey client.

/**************************************************************************/
[bugs #3761] Latest Modifications:

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 12/02/2003 at 22:01 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
            Severity | 5 - Average               | 7 - Major







/**************************************************************************/
[bugs #3761] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=3761>
Project: mldonkey, a free e-Donkey client
Submitted by: 0
On: Mon 05/26/2003 at 22:07

Category:  Core
Severity:  7 - Major
Item Group:  memory leak
Resolution:  None
Assigned to:  None
Status:  Open
Release:  None
Release:  release-2-5
Platform Version:  Linux i386-i686
Binaries Origin:  Compiled From CVS


Summary:  FT not respecting max sources per file settings

Original Submission:  Since yesterday, when I first tried 2-5 I suffer from 
mlnet taking large amounts of ram, often more than 450 MB (on a 368 MB ram 
machine) and I tried to track it down.



I guess now I accidently found whats causing the problem.

I added 7 FT files to my DL queue and each of the Files at least takes 900 
sources (some about 3600 sources each) and my max_sources_per_file is set to 
100 (which is respected by edonkey/overnet files).



With about 8000 sources for just 3 files 2 thinks are explained to me.

a) the high memusage

b) the large overhead I see atm after a few minutes of mlnet runningtime (line 
loaded with 85KB/s downtraffic while only 15kb are actually for the downloads), 
at mlnet starts its more like 40kb for dl, 5kb overhead.



But if mlnet really tries to connect that many sources periodically it surely 
will generate large overhead.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Sat 08/23/2003 at 14:28       By: None
on further inspection max_sources_per_file is a donkey option not involved in 
the FT code - but we do need an option for max sources per file on all 
networks. The FT code does limit the number of active sources to nranges - but 
nranges may be VERY large, and there is no maximum!

-------------------------------------------------------
Date: Sat 08/23/2003 at 14:04       By: None
I am seeing this same thing. For a time I thought it might be sources not 
stopping the download when they get to the end of a range, but it goes back to 
more overhead than download too fast for that.

I'm running 2.5-3 stable.














For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=3761>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/