flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-7310) always use HybridMemorySegment
Date Wed, 08 Nov 2017 13:20:00 GMT

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

Aljoscha Krettek closed FLINK-7310.
-----------------------------------
      Resolution: Fixed
    Release Note:   (was: Implemented in e14caef3794d0acde4bc86f67eedd8d032a3f213)

Implemented in e14caef3794d0acde4bc86f67eedd8d032a3f213

> always use HybridMemorySegment
> ------------------------------
>
>                 Key: FLINK-7310
>                 URL: https://issues.apache.org/jira/browse/FLINK-7310
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Core
>    Affects Versions: 1.4.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>             Fix For: 1.4.0
>
>
> For future changes to the network buffers (sending our own off-heap buffers through to
netty), we cannot use {{HeapMemorySegment}} anymore and need to rely on {{HybridMemorySegment}}
instead.
> We should thus drop any code that loads the {{HeapMemorySegment}} (it is still available
if needed) in favour of the {{HybridMemorySegment}} which is able to work on both heap and
off-heap memory.
> FYI: For the performance penalty of this change compared to using {{HeapMemorySegment}}
alone, see this interesting blob article (from 2015):
> https://flink.apache.org/news/2015/09/16/off-heap-memory.html



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

Mime
View raw message