avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-625) RPC: permit out-of-order responses
Date Thu, 02 Sep 2010 01:06:54 GMT

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

ryan rawson commented on AVRO-625:

Not sure exactly, but when multiple threads (lets say 50) all share 1 socket to talk to 1
regionserver (in my tests), the speed is capped below 13k ops/sec.  Freeing that, along with
some server-side fixes, we can hit past 21k.  The thing to remember is that HBase doesn't
stream data from disk ever - we read & cache data from HDFS, and in my test, the test
is 100% memory cached.  Also the more data you have to stream, the worse things become, mostly
because it takes a while to read out 64kbytes into a local array.  

The memory caching is key here, since everything comes from RAM we should be able to serve
at insane speeds, but this is just not the case, in part due to this connection sharing, also
in part due to server-side issues (Listener actually reading & deserializing data for
all connections) and so on.

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

View raw message