You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Andrey Zagrebin (Jira)" <ji...@apache.org> on 2019/10/10 17:07:00 UTC
[jira] [Commented] (FLINK-13984) Separate on-heap and off-heap
managed memory pools
[ https://issues.apache.org/jira/browse/FLINK-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948790#comment-16948790 ]
Andrey Zagrebin commented on FLINK-13984:
-----------------------------------------
We should add a release note:
The managed memory segment preallocation has been completely removed (Configuration option 'taskmanager.memory.preallocate'). It should not break the existing setups but setting this option will have no effect which can lead to a slight performance degradation as the segments will be allocated only in the ad-hoc manner during the execution.
> Separate on-heap and off-heap managed memory pools
> --------------------------------------------------
>
> Key: FLINK-13984
> URL: https://issues.apache.org/jira/browse/FLINK-13984
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Xintong Song
> Assignee: Andrey Zagrebin
> Priority: Major
>
> * Update {{MemoryManager}} to have two separated pools.
> * Extend {{MemoryManager}} interfaces to specify which pool to allocate memory from.
> Implement this step in common code paths for the legacy / new mode. For the legacy mode, depending to the configured memory type, we can set one of the two pools to the managed memory size and always allocate from this pool, leaving the other pool empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)