bench: order table rows by geometric mean across fixtures - #26
Closed
evoactivity wants to merge 1 commit into
Closed
bench: order table rows by geometric mean across fixtures#26evoactivity wants to merge 1 commit into
evoactivity wants to merge 1 commit into
Conversation
Arithmetic averaging would be dominated by the smallest fixture, so rows are ranked by geometric mean of op/s. Moves @tuananh/sax-parser to 2nd in streaming and 3rd in tokenization on the strength of its EPG results. Libraries that cannot parse a fixture rank by their per-fixture results rather than benefiting from the gap.
Owner
Author
|
Superseded by the per-fixture table restructure coming from bench/table-generator, which carries the geometric mean ordering in each section's overview table. |
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.
What
Orders the BENCHMARKS.md table rows by the geometric mean of op/s across each table's fixtures, and documents the rule in the methodology section.
Why geometric
An arithmetic mean would be dominated by the smallest, fastest fixture (DOM parsing's small column is 1.67M op/s against 19k for POM — the average would just re-sort by the small doc). The geometric mean weights every fixture equally, which is the standard way to average rates across workloads.
What moves
Libraries that cannot parse a fixture rank by their per-fixture results rather than benefiting from the gap: tXml's geomean over its completed fixtures would place it above default-validation Eksml in serialization despite losing every fixture the two share, so it stays below.
Follow-up to #24 — this commit was pushed to that branch just after it merged.