[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3766: Protocol is potentially high-latency and high bandwidth overhead for small files

[Tahoe-LAFS]

#3766: Protocol is potentially high-latency and high bandwidth overhead for small
files
-------------------------+---------------------------------------
 Reporter:  itamarst     |          Owner:  exarkun
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:  HTTP Storage Protocol
Component:  unknown      |        Version:  n/a
 Keywords:               |  Launchpad Bug:
-------------------------+---------------------------------------
 Imagine uploading a new, small file. As I understand it, this will
 require:

 1. Create a storage index.
 2. Upload each of the shares, e.g. 10 HTTP queries if there's 10 shares.

 One can't do _all_ queries in parallel, only uploads, because of the race
 condition between the uploads and the storage index existing. So even a
 clever, async client implementation will still require two HTTP roundtrips
 for each upload.

 In addition to double latency (or 11× latency for a naive client, which
 maybe we don't care about), there's also a bunch of HTTP protocol overhead
 for uploading a file.

 One can imagine an optimized variant of the API that includes both storage
 index and share creation in a single HTTP API call, for smaller files.
 This is, however, an optimization, and probably needn't exist in the first
 version.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3766>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage