[chore] Update benchmarks (again) #1586
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Benchmarks are hard. I find showing something rather than nothing is useful, but it needs so many caveats and asterisks. I also rounded the numbers (fairly) to reflect a lot of fluctuation they’ve had over time.
I feel like saying “openapi-fetch is faster” is an empty statement; benchmarks are important. However getting accurate benchmarks on how much faster is so tricky to get right. But I will always accept PRs like this that improve the accuracy and fairness of these benchmarks.
My overall goal is really not to be X-amount faster than alternatives. My only goal is to show that this is one of the fastest, if not the fastest, since I think fetch speed is so critical to applications.
How to Review
N/A
Checklist
N/A