-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Added benchmark suite #2153
Added benchmark suite #2153
Conversation
You can now specify a URL instead of a file. The benchmark program will automatically download and cache the file.
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.
This looks really interesting! What would it take to get across the line? Could I help out in some way?
I think this just needs a proper review. @mAAdhaTTah I looked over it again and did some minor refactoring. I think it's good to go but it would be nice if you could review it. |
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.
FWIW I think it looks good 👍🏽
@RunDevelopment I think this can be merged :) |
There's still one open comment. cc @mAAdhaTTah |
@RunDevelopment sorry, I approved, I don't think that change is necessary. |
@mAAdhaTTah Ahh ok. I always read "approved + comments" as "approved if all comments resolved". I'll keep that in mind in the future. |
In this case, I thought I had commented and resolved so that's my bad. |
This adds a benchmark suite to Prism.
Since I already explained everything in
benchmark.html
, I won't repeat myself but the basic idea is that the whole benchmark configuration is inbenchmark/config.js
.Points to discuss
I added support for multiple remote branches because it was easy and useful for testing my implementation but maybe we don't need it?It was pretty easy to implement, so let's just keep it.rn, I only display the mean, margin of error, and sample count. Anything else we need?More information can be added in future PRs if needed.The summary is quite simple, so maybe we could add something?It displays enough information IMO.