We have built 3 tools/services to help you evaluate RPC endpoint performance:
- Performance PRO
- Performance PUBLIC
- Performance INSPECTOR.
NODE BENCHMARKING is a different solution which is described in this section.
The performance suite as a whole has these characteristics:
- They use the same lambda probes in 27 AWS regions
- The runtime for these functions is Node.js 18 with the Axios library for rpc-json/http “transmission”
- In each case, lambdas are invoked separately to eliminate resource contention
- Their settings for each type of timeout is 5 seconds
- Regional telemetry is collected into DynamoDB tables for collation and charting.
PRO+PUBLIC vs. INSPECTOR
Both Performance PRO and PUBLIC are managed services. CompareNodes team does all the setup and maintenance such as adding / removing endpoints, providers etc.
On the other hand, Performance INSPECTOR is a public app. Any visitor can configure it and run it when they wish to do so using its launch form.
| Performance PRO+PUBLIC | Performance INSPECTOR | |
| Operation | Managed by CompareNodes | Self-service / public app |
| Duration | Runs perpetually 1-minute intervals | Each run is 30 seconds |
| Results | Charts, graphs Global+6 continents e.g. Fantom Mainnet PUBLIC | Tabular, export to .csv Global+6 continents & 27 regions e.g. Ankr vs. Blast API |
| Delivery | CompareNodes.com <iFrame> widgets for providers | Dedicated page for each result |
| Providers (endpoints) | 9 to 11 on the same page | 2 in each run |
| Networks | EVM, Substrate, UTXO | EVM, Substrate, UTXO |
Selection Criteria for Endpoints / Providers
You can use the Performance INSPECTOR for compatible networks from any provider as long as the endpoint is public or its authentication is the api-key in the URL/path (and not in the http-header).
Providers for the Performance PUBLIC pages are selected in the following way:
- When the page is sponsored by the protocol, we yield the selection decisions to the protocol team. E.g. Scroll team selects the providers for the Scroll Mainnet Public page because Scroll is the page sponsor.
- Other pages for Performance PUBLIC contain only the public endpoints which were in the top 10-11 when we did a comparison of public endpoints in our library of public endpoints. E.g. the selection of endpoints for the Fantom Mainnet PUBLIC page is described in the corresponding blogpost about the top public endpoints on Fantom Mainnet.
Performance PRO
These pages are sponsored by an individual provider. It is an exclusive service insofar as we offer only one such page per network — e.g. only one provider can sponsor Ethereum Mainnet PRO or Polygon Mainnet PRO. The sponsor of such a page chooses their cohorts while CompareNodes operates the pages. We ensure fair configuration and independent results. The primary differences between a network PUBLIC page and a corresponding PRO page is that all endpoints in the PUBLIC page are public endpoints whereas the PRO endpoints are always private endpoints. Moreover, the RPC methods are different. In case of EVM protocols, we use eth_blockNumber for Performance PUBLIC and eth_getBalance for Performance PRO.
Additional information is available in the FAQ section on the bottom of each performance page and the inspector launch form.
Become Performance PRO or PUBLIC Sponsor
Protocols can sponsor a Performance PUBLIC page for their protocol and gain an independent view of the public infrastructure available to their ecosystem.
Infrastructure providers can buy monthly or yearly subscriptions to Performance PUBLIC pages and receive an iFrame widget for their websites. As a marketing tool, these widgets can increase close rates for paid services.
Likewise, providers can contact us to discuss setup for Performance PRO pages.
Please use this form for any inquiries.
