Optimizing settings for VOD about p2p-media-loader HOT 2 CLOSED

bufferedSegmentsCount (P2P core)

It defines how many segments ahead of the current segment in the current track are taken into consideration by P2P algorithm to be downloaded (preferable via P2P) ahead of playhead position. For example VOD stream can contain 1000 segments but only limited by the parameter count of segments will be downloaded ahead of playhead position.

cachedSegmentsCount (P2P core)

The maximum number of downloaded segments (with payload) a peer keeps in the memory to share with others over P2P. The parameter limits memory usage.

forwardSegmentCount (Shaka Player specific)

It defines how many segments details ahead of the current segment we get using Shaka Player Manifest and pass to P2P algorithm. In most cases should be equal to bufferedSegmentsCount.

maxHistorySegments (Shaka Player specific)

It is not possible (or very hard) in shaka.net.NetworkingEngine determine by URL (and byte range) to what segment (and to what track) it belongs.
That is why when Shaka Player resolves next segment we store its details (URL, byte range, track etc.) in the cache - segments history.
Once Shaka Player requests the segment in shaka.net.NetworkingEngine we search for the segment by URL (and byte range) in this cache and recover its details.
The parameter defines the maximum number of segments in the cache to store to limit its size.

from p2p-media-loader.

@mrlika Thank you so much for the explanation!

from p2p-media-loader.