You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ryan rawson (JIRA)" <ji...@apache.org> on 2010/09/02 00:18:55 UTC

[jira] Commented: (AVRO-625) RPC: permit out-of-order responses

    [ https://issues.apache.org/jira/browse/AVRO-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905259#action_12905259 ] 

ryan rawson commented on AVRO-625:
----------------------------------

Note that in HBase land we have suffered heavily from the 1 socket per RPC endpoint pair policy.  In highly multithreaded apps our users find that they can't get the performance they desire due to this.  A few people have independently invented mechanisms to make this thread local that gives massive speedups in their clients.

Multiplexing multiple RPCs on the same socket is in other words not a clear gain when the RPC request and/or response may be significantly large. 

> RPC: permit out-of-order responses
> ----------------------------------
>
>                 Key: AVRO-625
>                 URL: https://issues.apache.org/jira/browse/AVRO-625
>             Project: Avro
>          Issue Type: New Feature
>          Components: java, spec
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.5.0
>
>
> It should be possible, when using a stateful, connection-based transport, for a client to complete a second request over a connection before the first request has returned.  In other words, responses should be permitted to arrive out-of-order.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.