Add CI check for performance impact

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Currently, changes in Parse Server are not evaluated based on their Parse Server performance impact. This can lead to "hidden" degradation of Parse Server that won't be discovered for a long time. When a performance issue is discovered, it is usually hard to pin down the root cause in retrospect.

Feature / Enhancement Description

Add CI check that evaluates performance impact.

Example Use Case

n/a

Alternatives / Workarounds

Unknown

3rd Party References

Unknown

[mtrezza]

@dplewis any idea how to go about this?

Could we use https://github.com/parse-community/benchmark or rather a 3rd part tool?

[dplewis]

@mtrezza I would recommend it since I built as a GitHub bot and we would have control over it or we could use some similar third party tool.

[mtrezza]

Maybe a 3rd party tool would be better as it relieves us of maintaining it.

For example https://github.com/rhysd/github-action-benchmark

It seems this does actually exactly what we need, incl. visualization and PR bot alert.

[dplewis]

I wish that was around 2 years ago lol. That is something we can look into.

Do Github Action VM's have the same specs every run? I assume so

[mtrezza]

Let's find out.

We could start with:

• Add https://github.com/bestiejs/benchmark.js with a simple test
• Add https://github.com/rhysd/github-action-benchmark to act on the benchmark values