... | ... | @@ -37,8 +37,18 @@ In the first semester of 2017, LEAP applied for a Mozilla grant with the aim to |
|
|
|
|
|
## Roadmap and current stage
|
|
|
|
|
|
The proposed roadmap was split in 5 activities.
|
|
|
The proposed roadmap was split in 5 activities:
|
|
|
|
|
|
* Creation of a live benchmark infrastructure to expose resource consumption statistics directly from the development repository tree.
|
|
|
* A minimal treatment of BLOBs/payloads as such instead of encoding them as strings as was previously done.
|
|
|
* Client-side transfer/crypto pipeline optimization.
|
|
|
* Server-side backend storage optimization.
|
|
|
* Server scalability.
|
|
|
|
|
|
Next, we address each item individually to give an account of its current state of development.
|
|
|
|
|
|
### Live benchmark statistics website
|
|
|
|
|
|
In July 2017 LEAP launched the https://benchmarks.leap.se/ website, where benchmarking statistics can be seen for every set of commits pushed to Soledad's repository. |
|
|
\ No newline at end of file |
|
|
In July 2017 LEAP launched the https://benchmarks.leap.se/ website, where benchmarking statistics can be seen for every set of commits pushed to Soledad's repository. We currently have time, memory and cpu consumption for each test of a special **benchmarking** set of tests. The solution is based on [elasticsearch](https://www.elastic.co/products/elasticsearch) to store results of benchmarks, [kibana](https://www.elastic.co/products/kibana) to plot graphs, and some custom scripts to glue everything together. Documentation on [how to add more tests to the benchmarking suite and website](http://soledad.readthedocs.io/en/latest/misc/benchmarks-website.html) is available.
|
|
|
|
|
|
As Soledad works with a reactor pattern, it is important to have feedback on possible reactor blocks and the overall reactor responsiveness. This is mostly done, but still not merged (#8908). |
|
|
\ No newline at end of file |