download: speak to as few servers as possible #448
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#448
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Our old roadmap.txt pointed out, in "Download Peer Selection step 2", that the current simplistic download code asks all known peers for the shares that they hold, whereas we really only need to ask enough peers to get "k" shares (plus a few extra in case we lose some during download, see #287).
This will probably occur about the same time we do a large-scale refactoring of the download code.
download: only speak to minimal number of peersto download: speak to as few servers as possible#605 (two-hour delay to connect to a grid from Win32, if there are many storage servers unreachable) is blocked on this ticket because I want to see if fixing this ticket (#448) improves (or otherwise changes) the behavior of the #605 issue.
If you like this ticket, you might also like the "Brian's New Downloader" bundle of tickets: #800 (improve alacrity by downloading only the part of the Merkle Tree that you need), #798 (improve random-access download to retrieve/decrypt less data), #809 (Measure how segment size affects upload/download speed.), #287 (download: tolerate lost or missing servers), and #605 (two-hour delay to connect to a grid from Win32, if there are many storage servers unreachable).
Brian's New Downloader is now planned for v1.8.0.
To what extent does the New Downloader address this ticket?
#798 resolves this ticket. The
ShareFinder
logic will send out multiple queries at once, so we'll wind up with more shares (and talk to more servers) that we strictly need, but it's limited to a window of 10 outstanding requests, which felt reasonable. (using something like3*k
might be more adaptive). And it will ask for more if it loses servers during the download. But it won't talk to the whole grid, which was the concern about this ticket.So I'm closing this one.
I created #1180 (put more DYHBs into flight at once when K is larger).