[Mldonkey-users] Swamping by LowID-Clients cause queue dropouts

[Sven Hartge]

Hi!

Someone mentioned, he gets swamped by LowID clients.

I now found the cause:

The max_clients_per_second value includes LowID and own connections.

If too many LowID clients connect to you, you will _never_ initate a
connection of your own.

Because of this, you drop out of the queue of nearly any direct client,
because you don't reconnect in the given time to renew the claim for
your slot.

I now increased the max_clients_per_second to 20 (!!) and guess what: I
am finally able to get some bytes for my rare files.

Please experiment with this setting, while leaving *every other* setting
_untouched_.

For the users downloading popular files, this shouldn't make any
difference, but for ones trying to get some rare files, this should
really improve the smootheness.

If you want to see the effect more clearly:

enable the logging of the connections to the gui console:

  set log_clients_to_console true

Then set max_clients_per_second to 1:

  set max_clients_per_second 1

and observe the console: you should see only LowID clients and after
some hours, the download-window will only list non-Direct clients as
queued, while the others are queued-out or not-connected.

The change max_clients_per_second to something higher:

  set max_clients_per_second 20

and observe the log once again: This time, you will see LowID and Direct
clients. The last ones are the connections initiated by your mldonkey,
because it now has enough "air" to connect to them on his own.

Soon after, the download-window will reveal: Yup, you get queued in
LowID _and_ Direct clients.

Hopefully someone is able to reproduce my observations.

S°

-- 
BOFH excuse #140:

LBNC (luser brain not connected)