[
https://issues.apache.org/jira/browse/FLINK-15172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingsong Lee resolved FLINK-15172.
----------------------------------
Resolution: Fixed
Merged in Master:
c11c696cca3b6ecafab605cceb36b7541444993f
56acfe9f666f590352453c9df6fbc385894de22f
f144e13acfe4ab37bfd9f65ae5cffd0b84fd78fe
adb595cd1445d0eefe9e23f85c79d8e9640cf07b
a907f29e24d27d1da9c981abed8ece2b211355eb
> Optimize the operator algorithm to lazily allocate memory
> ---------------------------------------------------------
>
> Key: FLINK-15172
> URL: https://issues.apache.org/jira/browse/FLINK-15172
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Runtime
> Reporter: Jingsong Lee
> Assignee: Jingsong Lee
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Now after FLINK-14063 , operators will get all manage memory of TaskManager,
> The cost of over allocate memory is very high, lead to performance regression
> of small batch sql jobs:
> * Allocate memory will have the cost of memory management algorithm.
> * Allocate memory will have the cost of memory initialization, will set all
> memory to zero. And this initialization will require the operating system to
> actually allocate physical memory.
> * Over allocate memory will squash the file cache too.
> We can optimize the operator algorithm, apply lazy allocation, and avoid
> meaningless memory allocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
