This is an automated email from the ASF dual-hosted git repository.
lzljs3620320 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-paimon.git
The following commit(s) were added to refs/heads/master by this push:
new c5d575220 [doc] Document using taskmanager.memory.managed.size
c5d575220 is described below
commit c5d575220996f00c6bdc938c9af778ebc2067c26
Author: JingsongLi <[email protected]>
AuthorDate: Tue Jun 27 16:32:15 2023 +0800
[doc] Document using taskmanager.memory.managed.size
---
docs/content/maintenance/write-performance.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/docs/content/maintenance/write-performance.md
b/docs/content/maintenance/write-performance.md
index 6e1f57c73..d229790c8 100644
--- a/docs/content/maintenance/write-performance.md
+++ b/docs/content/maintenance/write-performance.md
@@ -220,3 +220,8 @@ There are three main places in Paimon writer that takes up
memory:
* Memory consumed when merging several sorted runs for compaction. Can be
adjusted by the `num-sorted-run.compaction-trigger` option to change the number
of sorted runs to be merged.
* If the row is very large, reading too many lines of data at once can consume
a lot of memory when making a compaction. Reducing the `read.batch-size` option
can alleviate the impact of this case.
* The memory consumed by writing columnar (ORC, Parquet, etc.) file, which is
not adjustable.
+
+If your Flink job does not rely on state, please avoid using managed memory,
which you can control with the following Flink parameters:
+```shell
+taskmanager.memory.managed.size=1m
+```
