forked from quentin/quentin.dufour.io
WIP bittorrent
This commit is contained in:
parent
09972cb21f
commit
48b76cec9c
3 changed files with 117 additions and 83 deletions
56
_bibliography/bittorrent.bib
Normal file
56
_bibliography/bittorrent.bib
Normal file
|
|
@ -0,0 +1,56 @@
|
|||
@article{DBLP:journals/sigops/DemersGHILSSST88,
|
||||
author = {Alan J. Demers and
|
||||
Daniel H. Greene and
|
||||
Carl Hauser and
|
||||
Wes Irish and
|
||||
John Larson and
|
||||
Scott Shenker and
|
||||
Howard E. Sturgis and
|
||||
Daniel C. Swinehart and
|
||||
Douglas B. Terry},
|
||||
title = {Epidemic Algorithms for Replicated Database Maintenance},
|
||||
journal = {{ACM} {SIGOPS} Oper. Syst. Rev.},
|
||||
volume = {22},
|
||||
number = {1},
|
||||
pages = {8--32},
|
||||
year = {1988},
|
||||
url = {https://doi.org/10.1145/43921.43922},
|
||||
doi = {10.1145/43921.43922},
|
||||
timestamp = {Tue, 14 Jul 2020 14:25:20 +0200},
|
||||
biburl = {https://dblp.org/rec/journals/sigops/DemersGHILSSST88.bib},
|
||||
bibsource = {dblp computer science bibliography, https://dblp.org}
|
||||
}
|
||||
|
||||
|
||||
|
||||
@inproceedings{DBLP:conf/infocom/BharambeHP06,
|
||||
author = {Ashwin R. Bharambe and
|
||||
Cormac Herley and
|
||||
Venkata N. Padmanabhan},
|
||||
title = {Analyzing and Improving a BitTorrent Networks Performance Mechanisms},
|
||||
booktitle = {{INFOCOM} 2006. 25th {IEEE} International Conference on Computer Communications,
|
||||
Joint Conference of the {IEEE} Computer and Communications Societies,
|
||||
23-29 April 2006, Barcelona, Catalunya, Spain},
|
||||
year = {2006},
|
||||
crossref = {DBLP:conf/infocom/2006},
|
||||
url = {https://doi.org/10.1109/INFOCOM.2006.328},
|
||||
doi = {10.1109/INFOCOM.2006.328},
|
||||
timestamp = {Wed, 16 Oct 2019 14:14:51 +0200},
|
||||
biburl = {https://dblp.org/rec/conf/infocom/BharambeHP06.bib},
|
||||
bibsource = {dblp computer science bibliography, https://dblp.org}
|
||||
}
|
||||
|
||||
@proceedings{DBLP:conf/infocom/2006,
|
||||
title = {{INFOCOM} 2006. 25th {IEEE} International Conference on Computer Communications,
|
||||
Joint Conference of the {IEEE} Computer and Communications Societies,
|
||||
23-29 April 2006, Barcelona, Catalunya, Spain},
|
||||
publisher = {{IEEE}},
|
||||
year = {2006},
|
||||
url = {https://ieeexplore.ieee.org/xpl/conhome/4146652/proceeding},
|
||||
isbn = {1-4244-0221-2},
|
||||
timestamp = {Wed, 16 Oct 2019 14:14:51 +0200},
|
||||
biburl = {https://dblp.org/rec/conf/infocom/2006.bib},
|
||||
bibsource = {dblp computer science bibliography, https://dblp.org}
|
||||
}
|
||||
|
||||
|
||||
|
|
@ -1,83 +0,0 @@
|
|||
---
|
||||
layout: post
|
||||
slug: enseigner-le-cloud
|
||||
status: draft
|
||||
sitemap: true
|
||||
title: Enseigner le "cloud"
|
||||
description: Connection timed out
|
||||
categories:
|
||||
- systeme
|
||||
- enseignement
|
||||
tags:
|
||||
---
|
||||
|
||||
Apple, Adobe, Orange, SFR, Google, le _futur de la tech'_ ne serait se concevoir sans le cloud.
|
||||
Certaines mêmes vont plus loins, elles _sont_ le cloud comme OVH, autrefois hébergeur de site web, qui s'appelle maintenant OVHCloud.
|
||||
Le cloud fait également l'actualité, entre questions de souverainetés, de données ou encore de parts de marchés, il y a toujours un bon article à écrire.
|
||||
Le cloud est partout et maintenant jusque dans les universités et les écoles d'ingénieur... où je me suis retrouvé à l'enseigner.
|
||||
|
||||
|
||||
<div style="text-align:center">_Évolution de l'intérêt pour le sujet "cloud" sur Google_</div>
|
||||
|
||||
|
||||
Du TP qui nécessite une carte bancaire, au TP qui n'aura pas lieu car les infrastructures informatiques sont indiponibles en passant par le relai du discours des Amazon et consors sans prise de recul, cet article résume deux années de cours houleuses.
|
||||
|
||||
## Un concept dur à cerner
|
||||
|
||||
aa
|
||||
|
||||
#### L'histoire du mot et des offres commerciales
|
||||
|
||||
|
||||
A développé de nombreux outils pour
|
||||
Amazon a des ressources inutilisées
|
||||
sous traitance, externalisation
|
||||
|
||||
<!-- https://www.lesechos.fr/partenaires/econocom/comment-le-cloud-booste-les-entreprises-1034026 -->
|
||||
<!-- https://www.cairn.info/revue-communication-et-langages1-2014-4-page-77.htm -->
|
||||
<!-- http://www.slate.fr/story/91703/internet-mot-cloud -->
|
||||
|
||||
#### Un mot qui cache une réalité
|
||||
|
||||
On commence par la base : le cloud ce sont des ordinateurs. Beaucoup d'ordinateurs, allumés 24h/24. On les appelle des serveurs et on les place dans des datacenters.
|
||||
D'ailleurs, les serveurs et les datacenters existaient bien avant l'invention du mot cloud.
|
||||
|
||||
#### Pourquoi une telle addiction ?
|
||||
|
||||
L'objectif de notre cours, c'est de comprendre comment, avec ces serveurs on peut créer des Netflix, Google, Facebook, Twitter, Amazon, etc.
|
||||
C'est à dire des services qui ne tombent pas en panne, qui supportent des milliers (puis des millions et enfin des milliards) d'utilisateurs et qui ne coutent pas trop cher à maintenir.
|
||||
|
||||
C'est plus compliqué que ça, il y a un
|
||||
|
||||
#### Quels axes pour un cours
|
||||
|
||||
réseau
|
||||
|
||||
systèmes
|
||||
|
||||
systèmes distribués
|
||||
|
||||
architecture logiciel distribuée
|
||||
|
||||
## Place à la pratique
|
||||
|
||||
#### La sous-traitance comme modèle
|
||||
|
||||
|
||||
#### La nécessité d'avoir une infrastructure
|
||||
|
||||
Épuisement des ressources
|
||||
|
||||
Effets de bord en pagaille
|
||||
|
||||
Redémarrage des VMs
|
||||
|
||||
Coupures réseaux
|
||||
|
||||
Machines de TP
|
||||
|
||||
Migration qui échoue
|
||||
|
||||
SSE4.2 n'est plus disponible
|
||||
|
||||
|
||||
61
_posts/2020-10-22-understand-bittorrent.md
Normal file
61
_posts/2020-10-22-understand-bittorrent.md
Normal file
|
|
@ -0,0 +1,61 @@
|
|||
---
|
||||
layout: post
|
||||
slug: understanding-bittorrent
|
||||
status: draft
|
||||
sitemap: false
|
||||
title: Understanding BitTorrent
|
||||
description: From the network perspective
|
||||
categories:
|
||||
tags:
|
||||
- p2p
|
||||
- distributed system
|
||||
---
|
||||
|
||||
In this blog post, we will only review the core of BitTorrent.
|
||||
We are not interested in its extensions, its optimizations, how it manages spam, etc.
|
||||
|
||||
Compared to the specifications, we will focus our analysis on the importance of parameters and the emerging behaviours that arise when many BitTorrent clients communicate together.
|
||||
Moreover, as this (hopefully series of) article will be written in a goal to evaluate Peertube planned implementation of "webstream" (live-streaming over webtorrent), we will use the webtorrent implementation as reference for everything outside specifications.
|
||||
|
||||
We will also try to connect BitTorrent design to some academic papers to put things in perspective.
|
||||
|
||||
## A problem well stated is a problem half solved
|
||||
|
||||
**Discover content**
|
||||
|
||||
**Discover peers**
|
||||
|
||||
**Discover peers' content**
|
||||
|
||||
**Induce a desirable emerging behavior**
|
||||
|
||||
## The .torrent file
|
||||
|
||||
Describes the content of the file to download.
|
||||
Multiplexing.
|
||||
|
||||
## The role of the tracker
|
||||
|
||||
Discovering peers.
|
||||
What property it must enforce.
|
||||
Random sample of the network
|
||||
You will have some neighbors.
|
||||
|
||||
## Discovering the chunks known by your neighbors
|
||||
|
||||
introduce some Xerox Taxonomy {% cite DBLP:journals/sigops/DemersGHILSSST88 %}.
|
||||
"bitfield" puis "have" -> le push sur l'anti entropy
|
||||
If it's done symmetrically, we are in a push+pull model.
|
||||
|
||||
## Downloading the data
|
||||
|
||||
The importance of Local Rarest First {% cite DBLP:conf/infocom/BharambeHP06 %}
|
||||
|
||||
## Conclusion
|
||||
|
||||
BitTorrent is efficient as it multiplexes chunks.
|
||||
|
||||
## References
|
||||
|
||||
{% bibliography --cited %}
|
||||
|
||||
Loading…
Reference in a new issue