This is an automated email from the ASF dual-hosted git repository.
kassiez pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new fcd43e4118 [Improvement](docs) refine query acceleration doc (#1591)
fcd43e4118 is described below
commit fcd43e411874e5ac60714e8719edcbcc65c4a55b
Author: xzj7019 <xiongzhongj...@selectdb.com>
AuthorDate: Wed Dec 25 14:09:00 2024 +0800
[Improvement](docs) refine query acceleration doc (#1591)
## Versions
- [x] dev
- [ ] 3.0
- [ ] 2.1
- [ ] 2.0
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
.../performance-tuning-overview/analysis-tools.md | 8 ++++----
.../tuning/tuning-plan/adjusting-join-shuffle.md | 2 +-
.../tuning/tuning-plan/controlling-hints-with-cbo-rule.md | 4 ++--
docs/query-acceleration/tuning/tuning-plan/dml-tuning-plan.md | 2 +-
.../tuning/tuning-plan/optimizing-join-with-colocate-group.md | 4 ++--
.../tuning/tuning-plan/transparent-rewriting-with-async-mv.md | 2 +-
.../tuning/tuning-plan/optimizing-join-with-colocate-group.md | 2 +-
7 files changed, 12 insertions(+), 12 deletions(-)
diff --git
a/docs/query-acceleration/performance-tuning-overview/analysis-tools.md
b/docs/query-acceleration/performance-tuning-overview/analysis-tools.md
index c921000ab8..fc3e80044e 100644
--- a/docs/query-acceleration/performance-tuning-overview/analysis-tools.md
+++ b/docs/query-acceleration/performance-tuning-overview/analysis-tools.md
@@ -48,7 +48,7 @@ For cases of using Doris Explain output to perform plan-level
tuning, please ref
The Explain tool described above outlines the execution plan for an SQL query,
such as planning a join operation between tables t1 and t2 as a Hash Join, with
t1 designated as the build side and t2 as the probe side. When the SQL query is
actually executed, understanding how much time each specific execution step
takes—for instance, how long the build phase lasts and how long the probe phase
lasts—is crucial for performance analysis and tuning. The Profile tool provides
detailed executio [...]
-## Profile File Structure
+### Profile File Structure
A Profile file contains several main sections:
@@ -59,7 +59,7 @@ A Profile file contains several main sections:
5. The detailed information about the execution side is mainly contained in
the last part. Next, we will mainly introduce what information the Profile can
provide for performance analysis.
-## Merged Profile
+### Merged Profile
To help users more accurately analyze performance bottlenecks, Doris provides
aggregated profile results for each operator. Taking the EXCHANGE_OPERATOR as
an example:
@@ -96,7 +96,7 @@ In Doris, each operator executes concurrently based on the
concurrency level set
WaitForDependencyTime varies for each Operator, as the execution dependencies
differ. For instance, in the case of an EXCHANGE_OPERATOR, the dependency is on
data being sent by upstream operators via RPC. Thus, WaitForDependencyTime in
this context specifically refers to the time spent waiting for upstream
operators to send data.
-## Execution Profile
+### Execution Profile
Unlike the Merged Profile, the Execution Profile displays detailed metrics for
a specific concurrent execution. Taking the exchange operator with id=4 as an
example:
@@ -125,7 +125,7 @@ EXCHANGE_OPERATOR (id=4):(ExecTime: 706.351us)
In this profile, for instance, LocalBytesReceived is a metric specific to the
exchange operator and not found in other operators, hence it is not included in
the Merged Profile.
-## PipelineTask Execution Time
+### PipelineTask Execution Time
In Doris, a PipelineTask consists of multiple operators. When analyzing the
execution time of a PipelineTask, several key aspects need to be focused on:
diff --git
a/docs/query-acceleration/tuning/tuning-plan/adjusting-join-shuffle.md
b/docs/query-acceleration/tuning/tuning-plan/adjusting-join-shuffle.md
index c235b78047..181d101a42 100644
--- a/docs/query-acceleration/tuning/tuning-plan/adjusting-join-shuffle.md
+++ b/docs/query-acceleration/tuning/tuning-plan/adjusting-join-shuffle.md
@@ -1,7 +1,7 @@
---
{
"title": "Adjusting Join Shuffle with Hint",
- "language": "zh-CN"
+ "language": "en"
}
---
diff --git
a/docs/query-acceleration/tuning/tuning-plan/controlling-hints-with-cbo-rule.md
b/docs/query-acceleration/tuning/tuning-plan/controlling-hints-with-cbo-rule.md
index ba7a02f671..e57169b1e6 100644
---
a/docs/query-acceleration/tuning/tuning-plan/controlling-hints-with-cbo-rule.md
+++
b/docs/query-acceleration/tuning/tuning-plan/controlling-hints-with-cbo-rule.md
@@ -1,7 +1,7 @@
---
{
- "title": "Controlling Hints with CBO Rule",
- "language": "zh-CN"
+ "title": "Controlling CBO Rule with Hint",
+ "language": "en"
}
---
diff --git a/docs/query-acceleration/tuning/tuning-plan/dml-tuning-plan.md
b/docs/query-acceleration/tuning/tuning-plan/dml-tuning-plan.md
index c1f4324c10..418354590e 100644
--- a/docs/query-acceleration/tuning/tuning-plan/dml-tuning-plan.md
+++ b/docs/query-acceleration/tuning/tuning-plan/dml-tuning-plan.md
@@ -1,7 +1,7 @@
---
{
"title": "DML Tuning Plan",
- "language": "zh-CN"
+ "language": "en"
}
---
diff --git
a/docs/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
b/docs/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
index a5ead91e10..84cf8ba1c0 100644
---
a/docs/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
+++
b/docs/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
@@ -24,10 +24,10 @@ specific language governing permissions and limitations
under the License.
-->
-Defining colocate group is an efficient way of Join, through which the
execution engine can effectively avoid the transmission overhead of input data
in Join operations (for an introduction to Colocate Group, see
[JOIN](../../../query-data/join))
+Defining colocate group is an efficient way of Join, through which the
execution engine can effectively avoid the transmission overhead of input data
in Join operations (for an introduction to Colocate Group, see [Colocation
Join](../../colocation-join.md))
However, in some use cases, even if a Colocate Group has been successfully
established, the execution plan may still show as Shuffle Join or Bucket
Shuffle Join. This situation typically occurs when Doris is in the process of
data organization, for instance, it may be migrating tablets between BE to
ensure a more balanced distribution of data across multiple BE.
-You can view the Colocate Group status using the command `show proc
"/colocation_group"`; as shown in the figure below: If `IsStable` appears as
false, it indicates that there are unavailable `colocation_group` instances.
+You can view the Colocate Group status using the command `show proc
"/colocation_group"`; as shown in the figure below: If `IsStable` appears as
false, it indicates that there are unavailable `colocation group` instances.
\ No newline at end of file
diff --git
a/docs/query-acceleration/tuning/tuning-plan/transparent-rewriting-with-async-mv.md
b/docs/query-acceleration/tuning/tuning-plan/transparent-rewriting-with-async-mv.md
index 96be04741a..6665ddc194 100644
---
a/docs/query-acceleration/tuning/tuning-plan/transparent-rewriting-with-async-mv.md
+++
b/docs/query-acceleration/tuning/tuning-plan/transparent-rewriting-with-async-mv.md
@@ -1,7 +1,7 @@
---
{
"title": "Transparent Rewriting by Async-Materialized View",
- "language": "zh-CN"
+ "language": "en"
}
---
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
index 596098063e..b818931c2e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/tuning/tuning-plan/optimizing-join-with-colocate-group.md
@@ -24,7 +24,7 @@ specific language governing permissions and limitations
under the License.
-->
-Colocate Group 是一种高效的 Join 方式，使得执行引擎能有效地规避 Join 操作中数据的shuffle开销。相关原理介绍和案例参考详见
[Colocate-join](../../colocation-join.md)
+Colocate Group 是一种高效的 Join 方式，使得执行引擎能有效地规避 Join 操作中数据的shuffle开销。相关原理介绍和案例参考详见
[Colocation Join](../../colocation-join.md)。
:::tip 注意
- 在某些场景下，即使已经成功建立了 Colocate Group，执行计划（plan）仍然可能会显示为 `Shuffle Join` 或 `Bucket
Shuffle Join`。这种情况通常发生在 Doris 正在进行数据整理的过程中，比如，它可能在 BE 间迁移 tablet，以确保数据在多个 BE
之间的分布达到更加均衡的状态。
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
