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

Duong updated HDDS-9668:
------------------------
    Description: 
Today EC with GRPC copies input data buffer several times:
* when parsing protobuf objects from the input network stream, data is copied 
from the original netty direct buffer to heap. 
* when writing data to files, the heap buffer  needs to be copied to direct 
buffers by NIO.
The costs of buffer copies themself is inefficient, and the GC consequences of 
cleaning up the intermediate buffers slow the EC I/O down.

!ec-ncopies.png!


  was:
Today EC with GRPC copies input data buffer several times:
* when parsing protobuf objects from the input network stream, data is copied 
from the original netty direct buffer to heap. 
* when writing data to files, the heap buffer  !ec-ncopies.png! needs to be 
copied to direct buffers by NIO.
The costs of buffer copies themself is inefficient, and the GC consequences of 
cleaning up the intermediate buffers slow the EC I/O down.




> Zero-Copy in EC GRPC
> --------------------
>
>                 Key: HDDS-9668
>                 URL: https://issues.apache.org/jira/browse/HDDS-9668
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Duong
>            Priority: Major
>         Attachments: ec-ncopies.png
>
>
> Today EC with GRPC copies input data buffer several times:
> * when parsing protobuf objects from the input network stream, data is copied 
> from the original netty direct buffer to heap. 
> * when writing data to files, the heap buffer  needs to be copied to direct 
> buffers by NIO.
> The costs of buffer copies themself is inefficient, and the GC consequences 
> of cleaning up the intermediate buffers slow the EC I/O down.
> !ec-ncopies.png!



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to