... | ... | @@ -66,7 +66,7 @@ Starting with **0.10.0**, Soledad now has a proper BLOB infrastructure that deco |
|
|
|
|
|
## Client-side transfer/crypto pipeline optimization.
|
|
|
|
|
|
The following is a graph comparing the ratios of *Inbox loading time* having legacy JSON-based sync as baseline and blobs implementations with different features:
|
|
|
The following is a graph comparing the ratios of *Inbox loading time* for a certain amount of data (10MB), having legacy JSON-based sync as baseline and blobs implementations with different features, for several choices of partitioning of data:
|
|
|
|
|
|
![legacy-vs-blobs](/uploads/89dbd75715d466478cad7b8e6745de9a/legacy-vs-blobs.png)
|
|
|
|
... | ... | @@ -84,5 +84,7 @@ The implementations compared in the figure above are: |
|
|
* **Blobs + session cache:** same as above, but also caches session in server-side, thus avoiding having to query couch for user authentication data on every request.
|
|
|
* **Blobs + session cache + persistent http:** same as above, but also reuses HTTP connections on client side, thus avoiding having to open a new TLS/TCP connection for every request.
|
|
|
|
|
|
As it can be seen, the BLOBs implementation (with all the performance features) outperforms the legacy implementation for the same amount of data as the number of messages decrease and the size of each message increases.
|
|
|
|
|
|
## Server-side backend storage optimization.
|
|
|
## Server scalability. |
|
|
\ No newline at end of file |