Question regarding Torrents/Transmissions inner workings...

Discussion of Transmission that doesn't fit in the other categories
Post Reply
anomen
Posts: 1
Joined: Thu Jul 22, 2010 11:46 am

Question regarding Torrents/Transmissions inner workings...

Post by anomen »

Just to be clear about what I'm actually asking about:

Let's say I have created a torrent consisting of 100 files. It's active, and I'm currently the one seeding it to x number of peers.

When I have sent:
file #1-10 to peer #1
file #11-20 to peer #2
file #21-30 to peer #3 (for example)

So I still need to upload files #31-100, and along comes peer #4, who only has files #1-10 and asks me for an upload. My question is: Is the torrent system (or transmission specifically) smart enough to prefer to upload files #31-100 to peer #4 in this situation, or might it just as well be #11-30?

The point being, it makes more sense to upload 1 version of all the files before sending the same file numerous times, with regards to overall speed of the torrent and conservation of (my) bandwidth.

Anybody know?
...If not, that would be quite a future feature for transmission. ...Hint hint! And taking it a bit further, not limiting it to the initial seeder, but incorporating some way of knowing what the "rarest" file in the given torrent is, and preferring to seed that instead of other more available ones. ...Possible?

Edit:
"BTP/1.0 does not force a particular order for selecting which pieces to download. However, experience shows that downloading in rarest-first order seems to lessen the wait time for pieces. To find the rarest piece a client must calculate for each piece index the number of times this index is true in the bitfield vectors of all the neighboring peers. The piece with the lowest sum is then selected for requesting."

Does transmission do this?
Post Reply