Performance optimizations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 40
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] no need to wait for block if utxo is split into less than 25 outputs: ```INFO[21521] Splitting balance of 1.941 evenly between 19 UTXOs```
- [ ] Save blockchain.db files locally, don't keep going to / from S3
- [ ] parallelize yt-dl calls
- [ ] startup SDK + start calling yt-dl calls simultaneously, then wait for SDK startup
- [x] don't call video data on known failures (see https://github.com/lbryio/internal-apis/issues/1413)
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
The issue identifies four remaining areas: UTXO splitting, local caching of blockchain.db files instead of repeated S3 access, parallel yt-dl calls, and overlapping SDK startup with yt-dl calls. Start by tracing these workflows in ytsync and measuring their current behavior. Done means the unchecked optimization items are addressed and the affected workflows complete correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100