ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-01-18 18:56:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Forget about runtime performance

Browse Source
This commit is contained in:
Jean-Paul Calderone 2021-04-02 09:27:58 -04:00
parent c15fe70378
commit 89e1865f78
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/proposed/http-storage-node-protocol.rst
View File

@ -38,11 +38,7 @@ Tahoe-LAFS pays a substantial price:
The implementation is therefore the de facto standard and understanding of the protocol often relies on understanding that implementation.
* The Foolscap developer community is very small.
The implementation therefore advances very little and some non-trivial part of the maintenance cost falls on the Tahoe-LAFS project.
* The extensible serialization system imposes substantial overhead for the simple data structures Tahoe-LAFS exchanges.
* Foolscap encourages a "remote object" style of protocol design with involves many client-server interactions.
However, Foolscap does not implement "promise pipelining".
The result is that Foolscap encourages a protocol that requires many round-trips between client and server.
* The serialization overhead combined with the many round-trips result in Tahoe-LAFS presenting a more sluggish experience to users and taxes servers more greatly than is necessary.
* The extensible serialization system imposes substantial complexity compared to the simple data structures Tahoe-LAFS actually exchanges.
HTTP
~~~~