docs(developer-tools): reference OpenChainBench for live Berachain RPC latency#71
Open
Flotapponnier wants to merge 1 commit into
Open
docs(developer-tools): reference OpenChainBench for live Berachain RPC latency#71Flotapponnier 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 one line after the RPC and infrastructure providers list on
build/getting-started/developer-tools.mdxpointing readers to the OpenChainBench Berachain RPC benchmark for a live third-party latency comparison of the public no-key Berachain endpoints.Why
The developer-tools page currently lists every RPC provider self-describing performance. Developers picking an endpoint currently have no neutral datapoint to compare them side by side. OpenChainBench probes the public Berachain endpoints from three regions every minute and publishes p50, p95 and p99 latency under an open methodology.
Happy to reword, move, or drop if this does not fit the docs' tone.
Test plan