-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add CI tests for benchmarks. #658
Conversation
5113dd9
to
89cd507
Compare
a444cde
to
94bc282
Compare
This was implemented for some actions. Matching the behavior for all.
901e529
to
8173fd3
Compare
8173fd3
to
370c43f
Compare
fillDB $currentDataSize | ||
if [ -z "$minimal" ]; | ||
then | ||
flushDB |
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 flushing the db?
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.
it's a hack - we rely implicitly on building (npx tsc
) the Js utilities folder before running the node benchmark, because they share types.
Issue #, if available:
Allow benchmarks to run in a minimal fashion, that shouldn't take a long while.
Add CI task for each language, so that benchmarks will run for it.
Add relevant file extensions for changes that should trigger CI for each language.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.