You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per a discussion on call this week, we don't have anything currently handling/optimizing for multiple downloads at the same time. The connection manager would support concurrency and efficiency when finding peers.
Handle scenario where a poor connection has to download the same blob from multiple peers, effectively reducing their bandwidth at a single peer which means a successful download is less likely.
System Configuration
LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:
Anything Else
Screenshots
Internal Use
Acceptance Criteria
Definition of Done
Tested against acceptance criteria
Tested against the assumptions of user story
The project builds without errors
Unit tests are written and passing
Tests on devices/browsers listed in the issue have passed
QA performed & issues resolved
Refactoring completed
Any configuration or build changes documented
Documentation updated
Peer Code Review performed
The text was updated successfully, but these errors were encountered:
nice to have: separate connection opening from blob requests
why: so peers will take the time it needs to establish a connection before being available to download, thus improving the speed score and peer picking since the time to open the connection wont favor ongoing slower peers.
The Issue
Per a discussion on call this week, we don't have anything currently handling/optimizing for multiple downloads at the same time. The connection manager would support concurrency and efficiency when finding peers.
Handle scenario where a poor connection has to download the same blob from multiple peers, effectively reducing their bandwidth at a single peer which means a successful download is less likely.
System Configuration
Anything Else
Screenshots
Internal Use
Acceptance Criteria
Definition of Done
The text was updated successfully, but these errors were encountered: