[
https://issues.apache.org/jira/browse/TINKERPOP-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182885#comment-17182885
]
ASF GitHub Bot commented on TINKERPOP-2406:
-------------------------------------------
divijvaidya merged pull request #1311:
URL: https://github.com/apache/tinkerpop/pull/1311
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Delegate processing from event loop to worker threads
> -----------------------------------------------------
>
> Key: TINKERPOP-2406
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2406
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.4.8
> Reporter: Divij Vaidya
> Priority: Minor
>
> Netty client has two thread pools. Event loop thread pool which is
> responsible for handling socket events and another is a worker thread pool
> which is used to delegate busy work from event loop threads so that they can
> continue handling socket events. When programming in Netty, ideally, the
> event loop should never be blocked and must be kept free to respond to events.
> In case of exceptional completion of readComplete which could be triggered by
> a server sending an error code in the response, the event loop thread is used
> to perform the clean up logic which could involve an expensive
> replaceConnection. This blocks the event loop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
