You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 09:50:00 UTC

[jira] [Commented] (HADOOP-18533) RPC Client performance improvement

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

Shilun Fan commented on HADOOP-18533:
-------------------------------------

Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a blocker. Retarget 3.5.0.

> RPC Client performance improvement
> ----------------------------------
>
>                 Key: HADOOP-18533
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18533
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: rpc-server
>            Reporter: asdfgh19
>            Priority: Minor
>              Labels: pull-request-available
>
>   The current implementation copies the rpcRequest and header to a ByteArrayOutputStream in order to calculate the total length of the sent request, and then writes it to the socket buffer.
>   But if the rpc engine is ProtobufRpcEngine2, we can pre-calculate the request size, and then send the request directly to the socket buffer, reducing a memory copy. And avoid allocating 1024 bytes of ResponseBuffer each time a request is sent.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org