ERPC Announces Major Upgrade to Solana RPC, WebSocket, and Geyser gRPC Infrastructure — Significant Performance Improvement for Live Applications Compared to Major External RPC Services

ELSOUL LABO B.V. (Headquarters: Amsterdam, Netherlands; Representative Director CEO: Fumitake Kawasaki) and Validators DAO, which operate ERPC, are pleased to announce that they have implemented a major upgrade targeting the Solana RPC, WebSocket, and Solana Geyser gRPC infrastructure today.

This upgrade involved adding high-performance, large-scale nodes and comprehensively improving Solana RPC, WebSocket, Geyser gRPC, internal gateways, real-time data distribution adapters, network software, and server configurations. Performance has been enhanced along paths close to actual usage, based on accumulated data regarding load trends, subscription patterns, method-specific usage, and latency factors prone to occur in live applications.

In actual comparisons with major external RPC services in the same client environment in Frankfurt, ERPC demonstrated superior performance across multiple metrics crucial for live applications, including HTTP getSlot median, WebSocket connections, initial notification for WebSocket transactionSubscribe compatible functions, slot freshness, and errors.

This improvement is not limited to specific new plans but will be progressively reflected across all ERPC Solana RPC and Solana Geyser gRPC related plans. It will particularly have a significant impact on the user experience of Solana RPC and Geyser gRPC, and based on the improvements confirmed in Frankfurt, it will be sequentially applied to other regions.

ERPC Dashboard: https://dashboard.erpc.global/ja

ERPC Official Website: https://erpc.global/ja

Significant Performance Improvement for Live Applications Compared to Major External RPC Services

This comparison was conducted by measuring ERPC and major external RPC services under the same conditions from an identical client environment located in Frankfurt. The focus was on paths that are likely to lead to a noticeable difference in experience for live applications, such as HTTP getSlot, WebSocket slotSubscribe, and WebSocket transactionSubscribe compatible functions.

In representative actual measurement results, the median HTTP getSlot was 23.4ms for ERPC and 39.9ms for major external RPC services, making ERPC approximately 1.7 times faster. For WebSocket connections, ERPC was 87ms and major external RPC services were 157ms, making ERPC approximately 1.8 times faster. For the initial notification of WebSocket transactionSubscribe compatible functions, ERPC was 240ms and major external RPC services were 556ms, making ERPC approximately 2.3 times faster.

For Solana live applications, not only simple average latency but also connection establishment, initial notification, stability of real-time subscriptions, slot freshness, and the absence of errors are important. Especially for on-chain event detection, trading applications, monitoring systems, alert distribution, analysis platforms, bots, and backend APIs, how quickly the first notification arrives and how stably data can be received after starting a subscription determines the timing of subsequent processing.

In this comparison, ERPC and major external RPC services observed the same slot for processed and confirmed slot freshness. For WebSocket slotSubscribe, both also observed the same slot at the same time, indicating that ERPC showed an advantage in connection speed while having no difference in slot freshness. The number of errors was 0 for both.

Integrated Improvement of HTTP, WebSocket, and Geyser gRPC, Not Just Individually

This upgrade is not merely an improvement by adding servers. It involves an integrated review of Solana RPC's HTTP path, WebSocket path, Geyser gRPC path, internal gateways, real-time data conversion adapters, distribution processes, and network software.

In the actual operation of Solana applications, simply having a fast HTTP RPC is not sufficient. Slow WebSocket connections, delayed initial notifications, stagnant real-time subscription throughput, and Geyser gRPC performance issues can hinder overall application performance.