Opened 9 years ago

Last modified 2 years ago

#44 assigned enhancement

I2PSNARK --> Priority for torrents

Reported by: anonymous Owned by: zzz
Priority: minor Milestone:
Component: apps/i2psnark Version: 0.8
Keywords: Cc:
Parent Tickets:

Description

It would be very helpful if I2PSNARK supports priorities for torrents

Subtickets (add)

Change History (5)

comment:1 Changed 9 years ago by zzz

  • Owner set to zzz
  • Status changed from new to assigned

A generic priority system won't happen anytime soon, but maybe it could give more upload slots to incomplete torrents than complete torrents, so tit-for-tat works better.

comment:2 Changed 8 years ago by zzz

  • Type changed from task to enhancement

file priority within individual torrents is coming in 0.8.1.
But I think this ticket is asking for priorities among torrents.

comment:3 Changed 8 years ago by anonymous

  • Version set to 0.8

Provided that bandwidth is a pretty valuable resource in I2P, would it make sense to diminish the priority of torrents that don't have seeders?

Use-case example:

  • User adds torrent to I2PSnark
  • If no seeders present && majority (or percentage) of leechers haven't seen a complete file in $x amount of time (24h - 1 week?), don't start download

This could be seen in another way, from a leecher's perspective:

  • If local copy completeness < 50%, and no complete file seen in past 24h, don't send data to leechers who have < 1% of file.

Obviously, proper UI would be needed to inform the user.

comment:4 Changed 6 years ago by zzz

related: #1026

comment:5 Changed 2 years ago by slumlord

Per-torrent priority, especially based upon the criteria in comment 3, seems like a lot of work and of limited usefulness (though I could be wrong).

My opinion is that it should be up to the person downloading the torrent to determine if the torrent/swarm is worth the wait, if there are seeders, if there is a complete copy of the files across the swarm, etc. I do realize this ticket was opened 6-7 years ago, perhaps these changes/improvements aren't as important/useful now.

While writing this out I realized another thing: per-torrent upload/download slots. Perhaps on torrents that match the criteria laid out in comment 3, the user could manually set max upload/download slots of 1/1 to ensure that minimal bandwidth & resources are consumed by a torrent.

Last edited 2 years ago by slumlord (previous) (diff)
Note: See TracTickets for help on using tickets.