RequestWantedChunks Strategy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently we use a naive approach for deciding where to get the chunk from a list of peer who have the chunk.
This is NOT specified by the PPSPP spec, but there is a possible optimization step here to ensure the network load is evenly spread, or economically incentivized.
Related to https://github.com/livepeer/go-PPSPP/issues/14
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the current implementation that chooses a peer for requested chunks, then review the PPSPP specification and related issue #14. The issue does not identify files, tests, or a settled selection strategy; done would require agreeing on an optimization and validating that peer selection spreads network load or provides the intended incentive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100