[
https://issues.apache.org/jira/browse/AVRO-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905312#action_12905312
]
Doug Cutting commented on AVRO-625:
-----------------------------------
Ryan, I'm curious, what is the performance bottleneck with HBase when
connections are shared? In theory, with speed-of-light and switch delays,
multiple TCP streams are faster than a single stream, and perhaps that's what's
seen here, but I didn't think such effects came into play within a data center.
Also, if responses are streamed off of disk directly to the socket, then, in
theory, serializing responses over a single connection would limit throughput
to the speed of a single disk. But RPC responses are typically buffered before
they're written, so I wouldn't expect that to be a factor. Do you know what
the actual bottleneck is?
> 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.
