fix(speedtest): directory = exact public bench cohorts - #2242
Merged
Conversation
…gateways, non-benched chains)
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.
Review caught the raw harness config including probes that the public benches deliberately keep OFF the read-latency leaderboards: Flashbots Protect + bloXroute (scored on mev-protect-rpc, wrong axis here), blastapi, and 3 chains with no public bench. Directory is now cross-referenced with each benchmarks/-rpc.yml provider cohort: 87 chains / 274 endpoints, ethereum = exactly the 6 ranked providers. CORS preflight verified OK on the ethereum+base cohorts (Lava has a broken 410 preflight and will honestly show browser-blocked).