shortcut encryption and erasure coding when a file has already been uploaded #1508

Open
opened 2011-08-27 02:17:26 +00:00 by davidsarah · 0 comments
davidsarah commented 2011-08-27 02:17:26 +00:00
Owner

warner wrote in /tahoe-lafs/trac-2024-07-25/issues/6460#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

warner wrote in [/tahoe-lafs/trac-2024-07-25/issues/6460](/tahoe-lafs/trac-2024-07-25/issues/6460)#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
tahoe-lafs added the
code-encoding
major
enhancement
1.9.0a1
labels 2011-08-27 02:17:26 +00:00
tahoe-lafs added this to the undecided milestone 2011-08-27 02:17:26 +00:00
tahoe-lafs added
normal
and removed
major
labels 2012-03-29 19:34:20 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1508
No description provided.