klion26 commented on a change in pull request #8995:
FLINK-13106][doc-zh]Translate Parallel Execution page into Chinese
URL: https://github.com/apache/flink/pull/8995#discussion_r300818711
##########
File path: docs/dev/parallel.zh.md
##########
@@ -177,25 +159,18 @@ try {
</div>
-### System Level
+### 系统层次
-A system-wide default parallelism for all execution environments can be
defined by setting the
-`parallelism.default` property in `./conf/flink-conf.yaml`. See the
-[Configuration]({{ site.baseurl }}/ops/config.html) documentation for details.
+可以通过设置 ./conf/flink-conf.yaml 文件中的 parallelism.default 参数，在系统层次来指定所有执行环境的默认
parallelism。你可以通过查阅 [配置文档]({{ site.baseurl }}/zh/ops/config.html) 获取更多细节。
+获取更多细节。
-## Setting the Maximum Parallelism
+## 设置最大并发度
-The maximum parallelism can be set in places where you can also set a
parallelism
-(except client level and system level). Instead of calling `setParallelism()`
you call
-`setMaxParallelism()` to set the maximum parallelism.
+最大 parallelism 可以在所有设置 parallelism 的地方进行设定（除了客户端和系统层次）。与调用 `setParallelism()`
方法修改并发度相似，你可以通过调用 `setMaxParallelism()` 方法来设定最大 parallelism。
-The default setting for the maximum parallelism is roughly
`operatorParallelism + (operatorParallelism / 2)` with
-a lower bound of `127` and an upper bound of `32768`.
+默认的最大 parallelism 大致等于算子的 parallelism + 算子的 parallelism/2，其下限为 127，上限为 32768。
-<span class="label label-danger">Attention</span> Setting the maximum
parallelism to a very large
-value can be detrimental to performance because some state backends have to
keep internal data
-structures that scale with the number of key-groups (which are the internal
implementation mechanism for
-rescalable state).
+<span class="label label-danger">注意</span> 为最大 parallelism
设置一个非常大的值将会降低性能，因为一些 state backends 需要维持内部的数据结构，而这些数据结构将会随着 key-groups
的数目而扩张（key-groups 是 rescalable state 内部实现机制）
Review comment:
maybe `key-groups 是 rescalable state 内部实现机制` can be improved to `key-group
是状态重新分配的最小单元`
----------------------------------------------------------------
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:
us...@infra.apache.org
With regards,
Apache Git Services
