mldonkey-users
[Top][All Lists]
Advanced

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

Re: [Mldonkey-users] New source management


From: Alois
Subject: Re: [Mldonkey-users] New source management
Date: Mon, 23 Dec 2002 16:09:01 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20120912

Pierre Etchemaite wrote:

Where did you get those optimal settings ? :)

Santa Claus gave them to me :) No, these settings were just examples and don't mean anything, as I don't have much experiences with the edonkey protocol...

I hope that if any such scheme replaces the actual connection backoff + LRU,
the two will be heavyly tested one against the other, because more complex
algorithm don't always mean better performance.

In fact, complex algorithms can fail in many new and strange ways...

Of course it has to be tested VERY MUCH, and there would be also other problems:
Would there be one global queue or one queue for each file?
If there is a global queue, it could happen that one of the files has 10000 sources and all sources of other files fall out off the queue and have not one single source anymore. If there is a queue each file, the retry_delays wouldn't be respected, because a client could be in more than one queue because he has different files. And if the queue is too long, the number of sources, that have never been asked before could get too big and a new source is connected 4 hours after it was "new" the first time. And if you make too much difference between the types of clients (Emule, Overnet,...), it could happen that no single Emule is asked but Edonkeys are kind of flooded.

But I think that it is important that NOT EVERY new source is being asked, because this really generates too much traffic overhead, no matter which method is being used.





reply via email to

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