Throughput Benchmark Tool for RPC Endpoints

WHAT IT DOES

Throughput Benchmark Tool for RPC Endpoints measures the performance of EVM RPC endpoints by sending multiple eth_blockNumber requests and analyzing the results. You provide one or more RPC endpoint URLs, set the number of requests and concurrency level, and the tool runs a comprehensive benchmark. It measures throughput (requests per second), average response time, percentiles (p50, p95, p99), min and max latencies, error rates, and total duration. Results are displayed with color-coded performance indicators and a progress bar showing relative performance. This is essential for developers comparing RPC providers, evaluating infrastructure options, troubleshooting performance issues, or validating that a new RPC endpoint meets throughput requirements.

HOW TO USE

Enter RPC endpoint URLs—one per line—in the textarea. Set the number of requests per endpoint (default 100) and the concurrency level (default 10). Higher concurrency may trigger rate limits. Click "Run Benchmark." The tool sends eth_blockNumber requests to each endpoint with the specified concurrency, collects timing data, and calculates performance metrics. Results are displayed with a summary showing the fastest endpoint, individual result cards with detailed metrics, and a color-coded throughput indicator. Use the results to compare endpoints and identify the best performing option for your application.

THE REAL MECHANISM

The tool uses ethers.js v5.7.2's JsonRpcProvider to connect to each endpoint. For each benchmark run, it sends multiple eth_blockNumber requests in parallel batches controlled by the concurrency setting. The tool uses performance.now() to measure request timing with millisecond precision. It tracks completed requests, errors, and response times, then calculates statistics including throughput (completed requests divided by total duration), average response time, and percentile values (p50, p95, p99) from the sorted response time array. The tool processes endpoints sequentially to avoid cross-interference, and each endpoint receives the same number of requests. All benchmarking is done client-side—no data is sent to external servers beyond the RPC requests themselves.

WHAT IT CANNOT SEE

This tool cannot benchmark non-EVM RPC endpoints—it uses eth_blockNumber which is EVM-specific. It cannot simulate real-world RPC load patterns such as mixed method calls, varying payload sizes, or transaction submissions. It cannot measure network latency from the user's location accurately due to variations in internet routing and RPC node geographic distribution. It cannot detect RPC endpoint rate limits without sending many requests—the benchmark itself may trigger rate limits. It cannot benchmark authenticated or paid RPC endpoints requiring API keys without user-provided keys. It cannot test RPC methods that require state access—it only uses the lightweight eth_blockNumber method.

PLEASE NOTE

Throughput Benchmark Tool works exclusively with EVM-compatible RPC endpoints that support eth_blockNumber. It is a performance testing tool for developers, not an execution tool. All processing occurs client-side in your browser. The tool is free to use and does not require authentication. For best results, run benchmarks from the same network location as your application, and be aware that RPC endpoints may have rate limits that affect results.