Skip to content

fix: allow pubsub rpc to be processed concurrently #1

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

Conversation

achingbrain
Copy link

To allow processing pubsub messages that have steps that are slow but
async, process the messages in a queue.

Makes the concurrency configurable with a default of 10x messages.

To allow processing pubsub messages that have steps that are slow but
async, process the messages in a queue.

Makes the concurrency configurable with a default of 10x messages.
Copy link
Member

@wemeetagain wemeetagain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@wemeetagain wemeetagain merged commit f9e577d into ChainSafe:fix/process-concurrent-rpc Sep 17, 2021
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

Successfully merging this pull request may close these issues.

2 participants