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

Many peers disconnect when lots of transactions in a block are processed #345

Open
kdeme opened this issue Jun 28, 2019 · 2 comments

Comments

@kdeme
Copy link
Contributor

commented Jun 28, 2019

Problem as mentioned before, ideally we can offload this work. I did not debug this in dept, but I assume it is because we simply do no respond on certain requests, so the peers flags us as useless.
Created an issue here to remain aware that this happens.

@zah

This comment has been minimized.

Copy link
Member

commented Jun 28, 2019

Our current plan is to solve this by introducing a separate thread for the block processing. The network I/O thread will communicate with it through an AsyncChannel (currently being developed in Chronos).

@stefantalpalaru

This comment has been minimized.

Copy link
Contributor

commented Jun 28, 2019

a separate thread for the block processing

This is an embarrassingly parallel scenario, so it's worth using workers in a thread pool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.