You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by li...@apache.org on 2026/07/26 04:47:30 UTC

(seatunnel-website) branch main updated: [Docs] Add 2.3.13 Kubernetes CPU sizing guidance (#495)

This is an automated email from the ASF dual-hosted git repository.

davidzollo pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/seatunnel-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 5b0785e090f1 [Docs] Add 2.3.13 Kubernetes CPU sizing guidance (#495)
5b0785e090f1 is described below

commit 5b0785e090f1805889351bc7a1e9da622fc07540
Author: Daniel <es...@outlook.com>
AuthorDate: Sun Jul 26 12:47:24 2026 +0800

    [Docs] Add 2.3.13 Kubernetes CPU sizing guidance (#495)
---
 .../version-2.3.13/getting-started/kubernetes/kubernetes.mdx        | 6 +++---
 .../version-2.3.13/getting-started/kubernetes/kubernetes.mdx        | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx
index db5092786bb5..a5d99db2932d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx
@@ -535,10 +535,10 @@ spec:
             - '/opt/seatunnel/bin/seatunnel-cluster.sh -DJvmOption="-Xms16G -Xmx16G"'
           resources:
             limits:
-              cpu: "1"
+              cpu: "8"
               memory: 24Gi
             requests:
-              cpu: "1"
+              cpu: "4"
               memory: 20Gi
           volumeMounts:
             - mountPath: "/opt/seatunnel/config/hazelcast.yaml"
@@ -580,7 +580,7 @@ spec:
               path: seatunnel.streaming.conf
 ```
 
-此 Zeta 集群示例使用 16 GB JVM 堆内存。容器内存 request 设置为 20 GiB、limit 设置为 24 GiB,为 Metaspace、直接内存、线程栈和其他本地内存预留额外空间。对于大规模数据处理场景,建议使用 32 GB JVM 堆内存,并相应提高内存 request 和 limit,例如分别设置为 36 GiB 和 40 GiB。
+此 Zeta 集群示例使用 16 GB JVM 堆内存,CPU request 设置为 4、limit 设置为 8,容器内存 request 设置为 20 GiB、limit 设置为 24 GiB。内存余量用于 Metaspace、直接内存、线程栈和其他本地内存,CPU 配额用于任务执行、垃圾回收和引擎协调。对于大规模数据处理场景,建议使用 32 GB JVM 堆内存,可将 CPU request 和 limit 分别提高到 8 和 16,并将内存 request 和 limit 分别提高到 36 GiB 和 40 GiB,作为初始配置。请根据 Connector 特性、任务并行度以及实际 CPU、GC 和内存利用率继续调整。
 
 - 运行示例应用:
 ```bash
diff --git a/versioned_docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx b/versioned_docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx
index 6a85f0d20102..77f139ee99eb 100644
--- a/versioned_docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx
+++ b/versioned_docs/version-2.3.13/getting-started/kubernetes/kubernetes.mdx
@@ -535,10 +535,10 @@ spec:
             - '/opt/seatunnel/bin/seatunnel-cluster.sh -DJvmOption="-Xms16G -Xmx16G"'
           resources:
             limits:
-              cpu: "1"
+              cpu: "8"
               memory: 24Gi
             requests:
-              cpu: "1"
+              cpu: "4"
               memory: 20Gi
           volumeMounts:
             - mountPath: "/opt/seatunnel/config/hazelcast.yaml"
@@ -571,7 +571,7 @@ spec:
               path: seatunnel.streaming.conf
 ```
 
-This Zeta cluster example uses a 16 GB JVM heap. Its 20 GiB memory request and 24 GiB memory limit leave additional container memory for metaspace, direct memory, thread stacks, and other native memory. For large-scale data processing, a 32 GB JVM heap is recommended; increase the memory request and limit accordingly, for example to 36 GiB and 40 GiB.
+This Zeta cluster example uses a 16 GB JVM heap, requests 4 CPUs and 20 GiB of memory, and limits the container to 8 CPUs and 24 GiB of memory. The memory headroom is reserved for metaspace, direct memory, thread stacks, and other native memory, while the CPU allocation provides capacity for task execution, garbage collection, and engine coordination. For large-scale data processing, a 32 GB JVM heap is recommended; increase the CPU request and limit to 8 and 16, and the memory request a [...]
 
 - Starting a cluster:
 ```bash