fix(website): drop unweighted benchmark averages for per-workload counts#280
Merged
Merged
Conversation
…d counts Averaging a per-workload overhead ratio treats an 8x-costlier workload the same as a cheap one, so the mean is not meaningful. - Drop the "Average over JDBC" matrix footer. - Replace the average-overhead stat card with the entity-code line count. - Homepage cards now state how many of the eight workloads Storm wins against the selected library, and by how much it trails on the rest.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
The benchmark page and homepage reported unweighted averages of per-workload overhead ratios. Averaging a ratio across workloads of very different absolute cost (an 8x-costlier join counted the same as a cheap primary-key lookup) is not meaningful, so these are replaced with per-workload counts.