7.7 Building large P2PSP overlays

Although a P2PSP team can scale easily, there are several reasons why it might be desirable to split a large team into smaller ones. For example, if a team fails (for example, the splitter stop sending blocks to the peers), other teams would not be affected by this issue.


Figure 6: Two examples of an overlay with several teams. On At the left, the concurrency in the source is used to send in parallel the same stream towards two different teams. At the right, concurrency is created by an internal team. In both cases, the sub-teams are smaller than the original one.

Again, a solution to these problems consists in partitioning the big team into a collection of smaller ones. The simplest configuration makes use of the concurrent service that most of streaming servers can perform (see the schema at the left in the Figure 6). However, if the source node can not serve multiple streams, we can divide our big team following a tree structure where the root of the tree is the splitter connected to the source and peers are the leafs of the tree (see the schema at right in the Figure 6).



Creative Commons License
P2PSP (Peer-to-Peer Straightforward Protocol) by Cristobal Medina-López, J. A. M. Naranjo, L. G. Casado and Vicente González-Ruiz

is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.