docs: add RPC latency benchmark note to Public Endpoints - #5486
Closed
Flotapponnier wants to merge 1 commit into
Closed
docs: add RPC latency benchmark note to Public Endpoints#5486Flotapponnier 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Adds a short note after the RPC table pointing to an independent latency benchmark for Union's public endpoints.
The benchmark (OpenChainBench) continuously measures p50/p90/p99 round-trip latency for the public RPC endpoints listed in this table, probed every 60 seconds from us-east, eu-west, and Singapore. Nodes.Guru and Stake&Relax are already included.
Useful for developers choosing a reliable endpoint or debugging latency issues.
No code changes, documentation only.