[
https://issues.apache.org/jira/browse/HADOOP-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated HADOOP-4813:
--------------------------------
Description:
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).
was:
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).
Labels: newbie (was: )
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
