Re: Upload queue idea: Candidate selection based on on the response ratioDate: Thu, 4 Sep 2008 11:42:32 +0000 (UTC)

[email protected] Thu, 4 Sep 2008 13:42:33 +0200
Newsgroups gmane.network.gnutella.devel
Organization Home, Grenoble, France
Message-ID <[email protected]>
Quoting Arne Babenhauserheide <[email protected]> from ml.gnutella.dev-forum:
:But the FIFO strategy we currently have strongly favors big file downloads, 
:while small files are for what people mostly use Gnutella, so using FIFO seems 
:rather contraproductive. 

This is true, although a little bit less so with PARQ and multiple queues.
But still, within a PARQ queue you can have a wide range of file sizes,
and what you propose is interesting.

:The proposed selection strategy has the advantage of making downloads of small 
:files more efficient and removing the current unfairness without needing 
:multiple queues. 

Another thing which can probably be improved is the trade-off between
queuing and serving immediately.  For intance, if a client requests 20 KiB
only (e.g. to complete a small hole), it is silly to go through an active
queueing proces where the amount of headers exchanged will quickly reach
20 KiB anyway.  Short enough requests should be allowed to bypass any queuing
and be served immediately.

Note this has nothing to do with the file size.  You can request 20 KiB of
a 2 GiB file, it's still a small request.

Finally, clients should make sure download mesh exchanges take place during
the queuing exchanges.  It is useless to wait for the actual transfer to take
place to start exchanging sources.

Raphael