implement CHK download helper #268
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#268
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?
The upload-specific helper described in #116 is insufficient to achieve all
the properties we're hoping for. The helper as originally envisioned in that
ticket was specifically for uploading CHK files: it did not encompass
downloading files (since there's no bandwidth benefit for those), nor did it
include mutable files (since by our SDMF rules, these files are small and the
bandwidth of them isn't too much of a burden).
To prevent the clients from making connections to all storage servers, we
need a helper that will also mediate CHK downloads and mutable uploads and
downloads. I'm making a separate ticket for this since it's more work than
I'd originally realized. I think I can still get it done in the original
schedule.
Zooko and I have talked about the need or lack of need for this
connection-minimization. It may be the case that minimizing connections is
not all that important, at least with a reasonable number of clients. So it's
possible that we'll want the #116 upload-only helper to get us resumability
and 1x uploads, but not the all-purpose helper described in this ticket to
get us minimal connections and isolation between clients and storage servers.
I'm narrowing the focus of this ticket to just the CHK download helper. The
mutable-file helper has been moved off to #283, and the CHK-upload helper
remains in #116.
The benefit of implementing just the CHK-download helper is that downloads
will use a single TCP connection, improving bandwidth fairness. Specifically
this means that if both Tahoe and some other program are both downloading a
file over the same DSL line, they will get roughly the same bandwidth.
Without this feature, at our default 3-of-10 encoding, the Tahoe download
will get about three times as much bandwidth as the other program.
If all four helpers are implemented (#116, #268, and #283), then we can
change the introducer configuration to isolate the clients from the storage
servers.
implement rest of Helperto implement CHK download helperI'm pushing this out to 0.10.0 (i.e. post allmydata.com-final).
this one doesn't belong in 1.1.0
Perhaps this could be part of the solution to #868 (use helper to bypass NAT/firewall).