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

Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2017/08/25 10:21:00 UTC

[jira] [Updated] (FLINK-7512) avoid unnecessary buffer copies during network serialization

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

Nico Kruber updated FLINK-7512:
-------------------------------
    Description: 
Currently, we have our own {{Buffer}} class backed by a {{MemorySegment}} and whenever we try to write to or read from Netty, we need to copy to / from Netty's {{ByteBuf}} instances.

This is am umbrella task for avoiding these buffer copies and some related code changes

  was:
Currently, we have our own {{Buffer}} class backed by a {{MemorySegment}} and whenever we try to write to or read from Netty, we need to copy to / from Netty's {{ByteBuf}} instances.

This is am umbrella task for avoiding these buffer copies.


> avoid unnecessary buffer copies during network serialization
> ------------------------------------------------------------
>
>                 Key: FLINK-7512
>                 URL: https://issues.apache.org/jira/browse/FLINK-7512
>             Project: Flink
>          Issue Type: Improvement
>          Components: Network
>    Affects Versions: 1.4.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>
> Currently, we have our own {{Buffer}} class backed by a {{MemorySegment}} and whenever we try to write to or read from Netty, we need to copy to / from Netty's {{ByteBuf}} instances.
> This is am umbrella task for avoiding these buffer copies and some related code changes



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)