[infinispan-issues] [JBoss JIRA] (ISPN-5083) Hot Rod decoder should use async Cache operations

[Radim Vansa (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444304#comment-13444304 ] 

Radim Vansa commented on ISPN-5083:
-----------------------------------

[~gustavonalle] Does it make this request out-of-date? It's not just about being outside the IO loop, it's about being completely non-blocking, not consuming *any* threads while not active.

> Hot Rod decoder should use async Cache operations
> -------------------------------------------------
>
>                 Key: ISPN-5083
>                 URL: https://issues.jboss.org/browse/ISPN-5083
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Remote Protocols
>            Reporter: Galder Zamarreño
>            Assignee: Gustavo Fernandes
>             Fix For: 9.2.0.Final
>
>
> Hot Rod decoder is currently tying up Netty threads as a result of calling up to Infinispan sync operations. Instead, Hot Rod decoder should call up async operations, convert the Notifying Futures to Scala Futures, and write up the reply when it's received. This should increase performance specially under heavy load.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)