Benchmark Welo

[tabcat]

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.

• add benchmark for writes #43
• add benchmark for reads #44
• add benchmark for state calculation #45
• add benchmark for replication #46
• add benchmark for traversal #47
• add benchmark script to package.json
• github-action-benchmark pr comment
• github-action-benchmark gh pages chart

[tabcat]

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]

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

[tabcat]

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

[tabcat]

Current benchmarks are good enough to move forward