[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
   Resolution:               |   Keywords:
Launchpad Bug:               |
-----------------------------+-----------------------------------

Comment (by exarkun):

 > (or 11× latency for a naive client, which maybe we don't care about)

 Just to the point of such a naive client specifically: there are other
 motivations to not be this naive.  Primarily, all shares are produced at
 the same time as the cleartext is processed.  If you only upload one of
 them at a time, you have to store all the rest of them locally until
 you're ready to upload them.  If you upload in parallel (which the current
 Tahoe-LAFS does using the Foolscap protocol) then you never have to store
 any of them locally, you can stream them all up as they're generated.

 For small files, who cares.  But for large files this is likely to be
 pretty crummy - especially given ZFEC expansion which means you might end
 up storing 2x or 3x or more (technically the maximum is 255x I think, but
 that's not a very likely client configuration).

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