azagrebin commented on a change in pull request #10161: [FLINK-13986][runtime]
Clean up legacy code for FLIP-49.
URL: https://github.com/apache/flink/pull/10161#discussion_r352630980
##########
File path: docs/ops/config.md
##########
@@ -92,9 +92,9 @@ Configuration options to control Flink's restart behaviour
in case of job failur
{% include generated/task_manager_configuration.html %}
-For *batch* jobs Flink allocates a fraction of 0.7 of the free memory (total
memory configured via taskmanager.heap.size minus memory used for network
buffers) for its managed memory. Managed memory helps Flink to run the batch
operators efficiently. It prevents OutOfMemoryExceptions because Flink knows
how much memory it can use to execute operations. If Flink runs out of managed
memory, it utilizes disk space. Using managed memory, some operations can be
performed directly on the raw data without having to deserialize the data to
convert it into Java objects. All in all, managed memory improves the
robustness and speed of the system.
+For *batch* jobs Flink allocates a fraction of 0.6 of the total flink memory
(configured via taskmanager.memory.total-flink.size) for its managed memory.
Managed memory helps Flink to run the batch operators efficiently. It prevents
OutOfMemoryExceptions because Flink knows how much memory it can use to execute
operations. If Flink runs out of managed memory, it utilizes disk space. Using
managed memory, some operations can be performed directly on the raw data
without having to deserialize the data to convert it into Java objects. All in
all, managed memory improves the robustness and speed of the system.
Review comment:
0.6 -> 0.4
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
