Changes between Initial Version and Version 6 of Ticket #946
- Timestamp:
- 2010-04-25T15:42:45Z (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #946
- Property Keywords availability added
- Property Component changed from unknown to code-encoding
- Property Milestone changed from 1.7.0 to undecided
-
Ticket #946 – Description
initial v6 1 1 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. 2 2 3 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.3 This should have no negative 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. It can improve upload availability in some cases, by allowing up to {{{N-H}}} servers to fail or hang during the upload. 4 4 5 5 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).