hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4813) Avoid a buffer copy while replying to RPC requests.
Date Wed, 10 Dec 2008 05:54:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655105#action_12655105

Doug Cutting commented on HADOOP-4813:

> bytes on wire don't actually change. Is that approximately what you are proposing?

Yes.  We might add an output operation like, writeBuffer(ByteBuffer) that adds the stream's
current output buffer to the list if anything has been buffered, then adds the passed buffer,
and resets the stream's buffer

> Avoid a buffer copy while replying to RPC requests.
> ---------------------------------------------------
>                 Key: HADOOP-4813
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4813
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Raghu Angadi
> RPC server first serializes RPC response to a ByteArrayOutputStream and then creates
a new array to write to socket. For most responses the RPC handler is able to write the entire
response in-line. If we could use the same buffer used by ByteArrayOutputStream, we can avoid
this copy. 
> As mentioned in HADOOP-4802, yet another copy could be avoided (in most cases) if we
use a static direct buffer for the responses (not proposed for this jira).

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

View raw message