-
Notifications
You must be signed in to change notification settings - Fork 462
Description
The popularity of content is essential. Currently we do not have a method to determine if a magnet links points to a large swarms or a dying swarm.
This work enables novel caching approaches, see "Efficient analysis of caching strategies under dynamic content popularity".
Each peer in the network must contact a swarm to determine the size. Checking 1 swarm every 5 seconds to conserve bandwidth means it takes many hours to check several thousand swarms. It is possible to share this information with your neighbors. By gossiping this swarm size information around, swarms need to be checked only once and bandwidth is saved.
The swarm size community is mechanism to collaboratively determine the size of swarms. The step from magnet link to swarm size involves numerous steps. Resolving a magnet link means using the DHT mechanism. Checking a swarm and doing a bittorrent handshake also takes numerous UDP packets and dealing with non-responsive IPv4 addresses.
Experiments:
- App on Android Google Play market
- determine the exact bytes for each packet in the DHT and Bittorrent handshake and total lookup.
- determine the influence of swarm size on Video-on-demand performance (what is a healthy swarm size)
- how many neighbors do you need to collaborate with to make cooperation efficient
- credit mining / automagic caching of most popular content to boost system efficiency
- caching on Android: donate all your resources to Tribler (boost network with old/unused phones)
- boost with Raspberry Pi 3
Science:
- http://dl.acm.org/citation.cfm?id=1787254
- http://static.usenix.org/events/iptps/tech/full_papers/Dan.pdf
- http://ieeexplore.ieee.org/abstract/document/6761239/
- http://link.springer.com/chapter/10.1007/11758549_62
- http://ieeexplore.ieee.org/abstract/document/6193512/
- http://ieeexplore.ieee.org/abstract/document/6883812/
- http://ieeexplore.ieee.org/abstract/document/7218613/