hldb / welo

peer-to-peer, collaborative states using Merkle-CRDTs
Other
32 stars 2 forks source link

Benchmark Welo #37

Closed tabcat closed 1 year ago

tabcat commented 1 year ago

It's important to write benchmarks to understand the capability of the system and to track the effect of changes.

Will add benchmarks with benchmark.js and track them with github-action-benchmark.

tabcat commented 1 year ago

Because of how Benchmark.js works, either the database operations need to be more consistent or I have to to benchmark the database another way.

tabcat commented 1 year ago

Benchmarking the important metrics, replica read/write, another way until the database operations are more consistent seems like the best option.

tabcat commented 1 year ago

It's possible that I was not using Benchmark.js correctly with asynchronous code. Will have to check again.

tabcat commented 1 year ago

Current benchmarks are good enough to move forward