You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/21 19:06:43 UTC

[jira] [Resolved] (HADOOP-4813) Avoid a buffer copy while replying to RPC requests.

     [ https://issues.apache.org/jira/browse/HADOOP-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HADOOP-4813.
--------------------------------------

    Resolution: Incomplete

Closing as stale given the RPC engine has been replaced.

> Avoid a buffer copy while replying to RPC requests.
> ---------------------------------------------------
>
>                 Key: HADOOP-4813
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4813
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Raghu Angadi
>              Labels: newbie
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)