mldonkey-bugs
[Top][All Lists]
Advanced

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

[Mldonkey-bugs] [bugs #6239] max_upload_slots ignored


From: spiralvoice
Subject: [Mldonkey-bugs] [bugs #6239] max_upload_slots ignored
Date: Tue, 02 Dec 2003 15:47:48 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.5) Gecko/20031007

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

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

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

------------------ Additional Follow-up Comments ----------------------------
Please check if this bug is still in current CVS version.






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

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=6239>
Project: mldonkey, a free e-Donkey client
Submitted by: 0
On: Thu 10/30/2003 at 08:42

Category:  Core
Severity:  5 - Average
Item Group:  None
Resolution:  None
Assigned to:  None
Status:  Open
Release:  2.00
Release:  2.5-4
Platform Version:  Linux i386-i686
Binaries Origin:  Downloaded from Savannah


Summary:  max_upload_slots ignored

Original Submission:  Hi,



>From time to time, the number of active uploads gets out of control. 
>Max_upload_slots is set to 5, there is one directory shared with priority 3, 
>and incoming_directory_prio is  left at 0. So, I think I should never see more 
>than 8 active uploads at a time, however, sometimes there are as much as 30 
>upload slots used. Makes releasing rather painful, because the majority of 
>them uploads from temp, not from the shared dir. Apparently these extra 
>uploads come in bursts, like 10 slots with a CT of 50, another 8 with CT of 
>420, and so on...



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


-------------------------------------------------------
Date: Tue 12/02/2003 at 21:47       By: spiralvoice
Please check if this bug is still in current CVS version.

-------------------------------------------------------
Date: Thu 10/30/2003 at 23:15       By: None
Err... how long is a "good" connection time?:) I'll try this anyway, thanks for 
the tip.



But there is still a problem. As I understand the code, the limit is checked 
only when they ask for a new chunk, so there  will be 30 clients uploading at 
least 9.5MB at a terrific speed of 500 bytes/sec...



I'm not the only one experiencing that, see this thread:

http://mldonkey.berlios.de/modules.php?name=Forums&file=viewtopic&t=1379



-------------------------------------------------------
Date: Thu 10/30/2003 at 12:48       By: spiralvoice
You could try this patch 2126 to limit the connect time. I am also using 
directory upload priorities and sometimes the number of upload slots gets out 
of control, but 30... Never seen that. But slots with a connect time of 420 are 
really bad and will go away with the patch.












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

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





reply via email to

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