Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increasing Number of RPC Requests Impacting WebSocket Performance and CUU Metrics #369

Open
Rodebrechtd opened this issue Sep 18, 2024 · 1 comment

Comments

@Rodebrechtd
Copy link
Contributor

Rodebrechtd commented Sep 18, 2024

Issue Overview:

  • Rising number of RPC (Remote Procedure Call) requests via WebSocket.
  • Significant impact on CUU (Compute Units Used) per second and per month.
  • Topic requires further exploration to identify root causes.

Identified Concerns:

  • Logging operations consuming excessive compute resources.
  • RPC methods such as eth_sendRawTransaction and eth_estimateGas contributing to high compute usage.

Scalability Considerations:

  • Need to address scalability of WebSocket connections and processing capabilities.
  • Impact on gas fees as transaction volumes increase, leading to potential cost surges.

Required Actions:

  • Investigate the most compute-intensive operations
  • Analyze and optimize high-impact RPC methods.
  • Develop strategies to manage connection and compute scaling effectively.
  • Explore methods to mitigate rising gas fees under high transaction loads.
  • Consider a DRPC provider.
image image2 image3
@Rodebrechtd Rodebrechtd changed the title [story] Increasing Number of RPC Requests Impacting WebSocket Performance and CUU Metrics Increasing Number of RPC Requests Impacting WebSocket Performance and CUU Metrics Sep 18, 2024
@Rodebrechtd
Copy link
Contributor Author

The situation is fixed following this documentation - https://docs.lilypad.tech/lilypad/hardware-providers/setup-arbitrum-rpc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant