-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Automatically generate performance report #118
Comments
Additional benchmarks to look at: |
@fkleuver I think I've spent enough time with krausest benchmark to know what and how it does it.. |
Thanks, that would be awesome! My initial idea, for starters, was to simply duplicate the effective benchmarks but simplifying/cleaning up the infrastructure around it. I think the benchmarks as-is are pretty decent but we need some additional benchmarks as well, so we'll eventually need to break it open a bit and add some more interesting tests in there. But that's for later.
I don't know if you had any particular approach in mind but I'd suggest to start simple and just add the krausest repo to a PR as-is, stripping out every framework except vNext and vCurrent, and just work / clean it up from there. |
I think there should be a workflow.. to "add" vnext by tag.. |
Yep, if you could get a working setup in for starters then I can probably easily take care of that piece of automation.
We do probably want to leave artifacts anyway. I think they can live in a But if you feel this complicates things a bit too much I've no issues leaving that bit out for now. It's much more important to have a benchmark running regularly in the first place. We can just start with plain hard coded |
This is done now, right @fkleuver ? |
Not quite yet. We still need the performance report to include |
@fkleuver are we waiting on the azure/cosmos setup or can we close? |
Now that we have some e2e benchmark scripts, I'd like to see us have something a bit similar to the krausest benchmark with a generated HTML report showing:
The reason I didn't simply copy-paste their code is because I prefer fully understanding how it works, and then custom-tailoring it to include more specific information that is useful to us. Then perhaps in the future we can contribute some of our findings back to the krausest repo and hopefully improve the overall quality and accuracy of benchmark land
The text was updated successfully, but these errors were encountered: