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

Multithread Websockets to increase throughput #231

Merged
merged 1 commit into from
Dec 2, 2019

Conversation

shemnon
Copy link
Contributor

@shemnon shemnon commented Dec 2, 2019

Vertx by default orders all calls to executeBlocking in an ordered
fashion. As a side effect all requests are single threaded, even across
multiple clients. Because JSON-RPC has request identifiers it is not
needed to thread responses as they can be answered out of order. This
also allows multiple threads to handle requests, increasing throughput.

Signed-off-by: Danno Ferrin <[email protected]>

Release Notes

Performance Improvements in Websockets.

Vertx by default orders all calls to executeBlocking in an ordered
fashion.  As a side effect all requests are single threaded, even across
multiple clients. Because JSON-RPC has request identifiers it is not
needed to thread responses as they can be answered out of order.  This
also allows multiple threads to handle requests, increasing throughput.

Signed-off-by: Danno Ferrin <[email protected]>
@lucassaldanha lucassaldanha merged commit d643ad5 into hyperledger:master Dec 2, 2019
@shemnon shemnon deleted the websockets branch December 2, 2019 21:45
edwardmack pushed a commit to ChainSafe/besu that referenced this pull request Feb 4, 2020
Vertx by default orders all calls to executeBlocking in an ordered
fashion.  As a side effect all requests are single threaded, even across
multiple clients. Because JSON-RPC has request identifiers it is not
needed to thread responses as they can be answered out of order.  This
also allows multiple threads to handle requests, increasing throughput.

Signed-off-by: Danno Ferrin <[email protected]>
edwardmack pushed a commit to ChainSafe/besu that referenced this pull request Feb 4, 2020
Vertx by default orders all calls to executeBlocking in an ordered
fashion.  As a side effect all requests are single threaded, even across
multiple clients. Because JSON-RPC has request identifiers it is not
needed to thread responses as they can be answered out of order.  This
also allows multiple threads to handle requests, increasing throughput.

Signed-off-by: Danno Ferrin <[email protected]>
Signed-off-by: edwardmack <[email protected]>
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.

None yet

2 participants