Pond: The Oceanstore Prototype
SEDA. This is a fleck curious equally Pond does non look to convey a long workflow. Was SEDA necessary? Could it last avoided without loss of much performance? How critical was SEDA for the implementation.
The newspaper presents comprehensive evaluation results. While Pond does OK for reads (4 times faster than NFS) due to caching, its writes were boring (7 times slower than NFS) understandably due to erasure coding, threshold signed Byzantine agreement, together with versioning costs.
The newspaper presents comprehensive evaluation results. While Pond does OK for reads (4 times faster than NFS) due to caching, its writes were boring (7 times slower than NFS) understandably due to erasure coding, threshold signed Byzantine agreement, together with versioning costs.
0 Response to "Pond: The Oceanstore Prototype"
Post a Comment