You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "zhijiang (JIRA)" <ji...@apache.org> on 2018/09/21 06:41:00 UTC
[jira] [Commented] (FLINK-10339) SpillReadBufferPool cannot use
off-heap memory
[ https://issues.apache.org/jira/browse/FLINK-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623153#comment-16623153 ]
zhijiang commented on FLINK-10339:
----------------------------------
Hey [~NicoK] [~pnowojski], do you think we should make {{SpillReadBufferPool}} use direct memory as current {{NetworkBufferPool}} or are there any concerns to change this?
> SpillReadBufferPool cannot use off-heap memory
> ----------------------------------------------
>
> Key: FLINK-10339
> URL: https://issues.apache.org/jira/browse/FLINK-10339
> Project: Flink
> Issue Type: Improvement
> Components: Network
> Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
> Reporter: zhijiang
> Assignee: zhijiang
> Priority: Minor
>
> Currently, the {{NetworkBufferPool}} always uses off-heap memory to reduce memory copy from flink {{Buffer}} to netty internal {{ByteBuf}} during transporting on sender side.
>
> But for {{SpillReadBufferPool}} in {{SpilledSubpartitionView}}, it still uses heap memory for caching. We can make it as off-heap by default similar with {{NetworkBufferPool}} or decide the type by the current parameter {{taskmanager.memory.off-heap.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)