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

Gustavo Fernandes (JIRA) issues at jboss.org
Wed Apr 20 15:05:00 EDT 2016


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

Gustavo Fernandes commented on ISPN-5083:
-----------------------------------------

Netty IO threads should be free by using the extra executor introduced on ISPN-5342, do still think we should use cache async operations [~galderz]?

> 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.0.0.Alpha2
>
>
> 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.4.11#64026)



More information about the infinispan-issues mailing list