docs(rpc): add OpenChainBench live RPC benchmark reference - #2761
docs(rpc): add OpenChainBench live RPC benchmark reference#2761Flotapponnier wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a short documentation section pointing readers to an external service for live Stellar RPC latency benchmarks.
Changes:
- Introduces a new “Benchmarks” section to the RPC providers doc
- Links to OpenChainBench for p50/p90/p99 latency comparisons across regions
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| | [Ankr](https://www.ankr.com/rpc/stellar) | Mainnet | Full Archive RPC `https://rpc.ankr.com/stellar_soroban` | | ||
| ## Benchmarks | ||
|
|
||
| For live latency comparisons across Stellar RPC providers, see [OpenChainBench](https://openchainbench.com) — an open-source benchmark tracking p50/p90/p99 latency for Stellar RPC providers, probed every minute from 3 global regions (US, EU, Asia). |
There was a problem hiding this comment.
Good point. Updated the text to clarify scope and add a one-liner on percentile interpretation:
Measurements are best-effort and reflect client-side HTTP round-trip times from 3 fixed probe origins (Virginia, Amsterdam, Singapore); actual latency from your application depends on your deployment region and provider routing. p50 is the median response time (half of requests are faster), p90 means 90% of requests finish within that time, and p99 captures the slowest 1% — useful for spotting tail-latency outliers under real load.
Will push the update to the branch shortly.
OpenChainBench (https://openchainbench.com) is an open-source benchmark tracking p50/p90/p99 latency for Stellar RPC providers, probed every minute from 3 global regions. Adding a Benchmarks section at the end of the RPC providers page gives developers a live reference when choosing between providers.