-
Notifications
You must be signed in to change notification settings - Fork 132
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
chore: add performance benchmark with hyperfine #1089
Conversation
6460988
to
43c1eb7
Compare
Coverage report
Test suite run success585 tests passing in 85 suites. Report generated by 🧪jest coverage report action from 35c4bbe |
43c1eb7
to
955c836
Compare
🚀 |
c6c118a
to
aebeb3e
Compare
|
🚀 |
a724277
to
06a616a
Compare
|
bc14580
to
bbfeed0
Compare
|
bbfeed0
to
b650185
Compare
|
b650185
to
c22f858
Compare
|
c440127
to
5068589
Compare
5068589
to
0cf8335
Compare
- name: Install External | ||
run: npm i -g hyperfine @redocly/cli@latest |
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.
should it compare with the latest or with the version from main?
I think latest is fine for now but would be great to check-out main branch and compare it to it somehow in the future.
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.
Yes, comparing to main would be better, but I haven't found a simple and reliable solution to this yet. Will check how this approach works first, and then we can decide how to evolve it.
36248c8
to
35c4bbe
Compare
What/Why/How?
Added performance benchmarking using
hyperfine
.Reference
Testing
Screenshots (optional)
Check yourself
Security