[
https://issues.apache.org/jira/browse/IGNITE-11685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883794#comment-16883794
]
Aleksey Plekhanov commented on IGNITE-11685:
--------------------------------------------
[~Pavlukhin], [~isapego] thanks for the review.
I've done benchmarks, there is about 2% performance drop in the single thread
mode in the worst case (in-memory atomic cache, single localhost server node
without network delays), but I see no ways how to get rid of any added
synchronizators or data-structures and still preserve async mode and
thread-safety. Perhaps, if we will really need this 2% for some corner case in
the future we can add a new parameter to the configuration (sync or async mode).
Merged to master.
> Java thin client: Handle multiple async requests in parallel
> ------------------------------------------------------------
>
> Key: IGNITE-11685
> URL: https://issues.apache.org/jira/browse/IGNITE-11685
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: iep-34
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> In the current implementation {{ReliableChannel}} uses an exclusive lock to
> send a request and waits for response synchronously. In this implementation,
> there are no benefits of using multiple threads. To improve throughput and
> latency we can implement async request/response processing on the client
> side, since the server side is already async.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
