[tahoe-dev] [tahoe-lafs] #946: upload should succeed as soon as the servers-of-happiness criterion is met

[tahoe-lafs]

#946: upload should succeed as soon as the servers-of-happiness criterion is met
--------------------------------+-------------------------------------------
 Reporter:  davidsarah          |           Owner:  nobody
     Type:  enhancement         |          Status:  new   
 Priority:  major               |       Milestone:  1.7.0 
Component:  unknown             |         Version:  1.6.0 
 Keywords:  performance upload  |   Launchpad_bug:        
--------------------------------+-------------------------------------------
 The performance of upload could be improved by returning success to the
 client as soon as the servers-of-happiness criterion is met, rather than
 when all shares have been placed. The storage client would continue to
 upload the remaining shares asynchronously.

 This should have no impact on preservation or availability, because once
 the happiness criterion has been met, we know that we are going to return
 success to the client even if no further shares can be placed.

 Upload performance should be improved in a similar way to #928's
 improvement of download performance (although less dramatically, since
 with the default parameters, we will be returning after shares have been
 uploaded to the fastest 7 servers, rather than after shares have been
 downloaded from the fastest 3 servers as for #928).

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/946>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid