[ 
https://issues.apache.org/jira/browse/IGNITE-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216952#comment-17216952
 ] 

Ignite TC Bot commented on IGNITE-13595:
----------------------------------------

{panel:title=Branch: [pull/8368/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8368/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: Basic Tests* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5674947&buildTypeId=IgniteTests24Java8_RunBasicTests]

> 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)

Reply via email to