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

Single message processing optimizations #296

Open
cam-schultz opened this issue May 22, 2024 · 0 comments
Open

Single message processing optimizations #296

cam-schultz opened this issue May 22, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@cam-schultz
Copy link
Collaborator

Context and scope
Once #31 is implemented, individual Warp messages will be processed in their own goroutines, significantly increasing the overall application throughput when compared to the serial processing approach. However, there still remains opportunities to optimize the individual message processing jobs, targeting end-to-end single message latency. Some known examples include:

  • Reducing the number of blocking RPC calls to API nodes
  • Improving the locking logic on the inbound request handler singleton
  • Consider processing incoming blocks async, to mitigate incoming block queue growth

#185 may provide insight into other bottlenecks that are good optimization targets. We should also explore tools such as flame graphs to identify hotspots.

@cam-schultz cam-schultz added the enhancement New feature or request label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog 🗄️
Development

No branches or pull requests

1 participant