docs(fraxtal): reference OpenChainBench for live RPC latency comparison#174
Open
Flotapponnier wants to merge 1 commit into
Open
docs(fraxtal): reference OpenChainBench for live RPC latency comparison#174Flotapponnier wants to merge 1 commit into
Flotapponnier wants to merge 1 commit into
Conversation
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
Adds a short
Benchmark Provider Latencysection at the end ofpages/fraxtal/network/network-information.mdxpointing readers to the OpenChainBench Fraxtal RPC benchmark for a live third-party latency view of the public Fraxtal endpoints.Why
The page lists both the official Fraxtal RPC endpoints and third-party providers (dRPC, Tenderly, Grove, Nirvana, Opsec, QuickNode). Developers picking an endpoint currently have no neutral datapoint to compare them side by side. OpenChainBench probes the public Fraxtal endpoints from three regions every minute and publishes p50, p95 and p99 latency under an open methodology.
Happy to reword, move to a different position, or drop if this does not fit the docs' tone.
Test plan