Maximum rate of blob announcement is too low for big seeders
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
I have been measuring the number of blobs that my LBRY daemon can announce. The maximum rate appears to be about 100 per hour, or 2400 per day (my measurements are live at https://keybase.pub/brendonbrewer/blob_announce_test/results.png). That implies I can only successfully host about 1200 streams, as two blobs per stream need to be announced once every 24 hours.
I discussed this with Jack on tech-guests, who said the following, which doesn't sound too complicated (for him).
"we could do a refactor to do batch announcements a lot more minimally"
I decided to make an issue to increase the chance this gets implemented soon. :-)
Contributor guide
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
Start by reproducing the reported blob-announcement rate using the linked measurement results, then trace the daemon's announcement path to find where batch announcements are handled. Done means demonstrating that the daemon can announce substantially more blobs while preserving the required once-per-day coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100