[tahoe-lafs-trac-stream] [tahoe-lafs] #1508: shortcut encryption and erasure coding when a file has already been uploaded

[tahoe-lafs]

#1508: shortcut encryption and erasure coding when a file has already been
uploaded
--------------------------------------------+---------------------------
 Reporter:  davidsarah                      |          Owner:
     Type:  enhancement                     |         Status:  new
 Priority:  major                           |      Milestone:  undecided
Component:  code-encoding                   |        Version:  1.9.0a1
 Keywords:  upload performance convergence  |  Launchpad Bug:
--------------------------------------------+---------------------------
 warner wrote in ticket:1398#comment:6 :
 > '''publishing immutable when the file is already uploaded''': our
 Uploader doesn't short-circuit the upload when it discovers that enough
 shares are already in place. The upload sequence runs (including
 encryption and erasure-coding of each share), but the results are
 discarded. (this is arguably an inefficiency, but I'm not convinced the
 additional code paths would be worth it). So the memory footprint is the
 same as for not-already-uploaded

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1508>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage