[Mldonkey-bugs] [bug #14468] max_hard_upload_rate erratic behavior (load sensitive)

[Jonathan Thibault]

URL:
  <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14468>

                 Summary: max_hard_upload_rate erratic behavior (load
sensitive)
                 Project: mldonkey, a multi-networks file-sharing client
            Submitted by: finboyslick
            Submitted on: Thu 09/08/05 at 05:05
                Category: Core
                Severity: 3 - Normal
              Item Group: Program malfunction
                  Status: None
             Assigned to: None
             Open/Closed: Open
                 Release: 
                 Release: 2.6.3
        Platform Version: Linux
         Binaries Origin: CVS / Self compiled
                CPU type: Intel x86

    _______________________________________________________

Details:

As discussed in the #mldonkey channel, mlnet seems to have a flaw with upload
bandwidth throttling.  I've experimented and tested a lot and found out a few
things:

It seems to be CPU related.  Though a bit underpowered (pIII 550), the box I
use for mldonkey is almost exclusively dedicated to it.  If I reset the
max_hard_upload_rate value, I will get 'normal' behavior for a while.  That
is an upload rate that keeps very close to its limit.  How long normal
behavior lasts seems to be closely related to the load on the machine.  If I
start a compile job or anything processor intensive, the upload rate will
significantly drop (from 60k/sec to as low as 5k/sec).

Even if I leave the box alone, upload rate will only remain stable (mosly
flat graph) for so long, longer on more powerful machines (I tested an Athlon
XP 1.7, it took about 30 minutes).  Once the upload rate starts behaving like
that (spikey graph), it will not return to a stable rate until it is reset. 
That is, max_hard_uload_rate = 0, then max_hard_upload_rate = 60.

>From earlier discussions in #mldonley with Amorphous, it would appear that
the behavior can be reproduced.  It would also confirm that the stronger the
box, the longer it takes for the problem to manifest.

I've included a sancho screenshot of what happens when the only thing loading
the box is mlnet itself.  (no GUI, etc.)





    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Thu 09/08/05 at 05:05  Name: example3.png  Size: 198.75KB   By:
finboyslick
Sancho stats screenshot.
<http://savannah.nongnu.org/bugs/download.php?item_id=14468&item_file_id=2931>

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14468>

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