[
https://issues.apache.org/jira/browse/IGNITE-13496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239206#comment-17239206
]
Pavel Tupitsyn commented on IGNITE-13496:
-----------------------------------------
Using more than one selector ({{GridNioServer.Builder.selectorCount}}) does not
improve performance in a few use cases that I tried: large and small entries
(from 10 KB to 10 MB), 4 to 16 threads, 4 to 16 cluster nodes.
> Java thin: Use non-blocking socket IO
> --------------------------------------
>
> Key: IGNITE-13496
> URL: https://issues.apache.org/jira/browse/IGNITE-13496
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Affects Versions: 2.9
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Fix For: 2.10
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> IGNITE-7623 introduces async APIs to the Java thin client. However, socket
> writes still cause user thread blocking and thus reduce scalability.
> Investigate and prepare an IEP to use non-blocking IO.
> This ticket does not affect user-facing APIs, only changes the way we do IO
> internally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
