-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cut down on benchmarking metrics to improve build speeds #167
Conversation
.add('simple - parse', function () { | ||
parse(simpleQuery); | ||
}) | ||
.add('simple - highlight', function () { | ||
parserWrapper.clearCache(); | ||
applySyntaxColouring(simpleQuery); | ||
}) | ||
.add('simple - validate syntax', function () { | ||
parserWrapper.clearCache(); | ||
validateSyntax(simpleQuery, benchmarkingMediumSizeSchema); | ||
}) | ||
.add('simple - autocomplete next statement', function () { | ||
parserWrapper.clearCache(); | ||
autocomplete(simpleQuery, benchmarkingMediumSizeSchema); | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we removing benchmarks? Wouldn't it be better to leave them but just run them on merge to main
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was in the "reduce gh minute" mindset, so I removed some that didn't feel like they were super impactful, to see if the build got noticeably faster. But you're right, I think we're better off keeping them - i added them back now
* cut down on bench tests to make the job faster * don't run on PRs * keep benchmarks
Let's set something up in grafana for alerts, rather than build twice on the PR itself 👍