Closed tabcat closed 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.
Benchmarking the important metrics, replica read/write, another way until the database operations are more consistent seems like the best option.
It's possible that I was not using Benchmark.js correctly with asynchronous code. Will have to check again.
Current benchmarks are good enough to move forward
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.
#44#45#46#47github-action-benchmark pr commentgithub-action-benchmark gh pages chart