[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=13028002#comment-13028002 ] 

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

Could you elaborate in what situations this should help? It seems to me that you only delegate the work to another thread pool, which will get exhausted soon. What do you intend to use as rejection policy?

> 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: 7.1.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
(v6.3.11#6341)