You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/10/19 13:14:00 UTC
[jira] [Commented] (IGNITE-13595) Java thin client: Redundant CHM
get/remove on each request to server
[ https://issues.apache.org/jira/browse/IGNITE-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216708#comment-17216708 ]
Aleksey Plekhanov commented on IGNITE-13595:
--------------------------------------------
[~ptupitsyn], [~timonin.maksim], can you please review this tiny patch?
> Java thin client: Redundant CHM get/remove on each request to server
> --------------------------------------------------------------------
>
> Key: IGNITE-13595
> URL: https://issues.apache.org/jira/browse/IGNITE-13595
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we have two redundant ConcurrentHashMap calls ({{pendingReqs.get(reqId)}}, {{pendingReqs.remove(reqId)}}) in {{TcpClientChannel#receive}} and {{TcpClientChannel#receiveAsync}}. These calls are redundant since we can provide {{pendingReq}} by {{send}} method, and remove it from {{pendingReqs}} when receive response for request. This will reduce each request latency for a little bit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)