Skip to content

refresh TopSQL docs and screenshots#21431

Open
yibin87 wants to merge 20 commits intopingcap:masterfrom
yibin87:update_topsql_functionality
Open

refresh TopSQL docs and screenshots#21431
yibin87 wants to merge 20 commits intopingcap:masterfrom
yibin87:update_topsql_functionality

Conversation

@yibin87
Copy link
Copy Markdown
Contributor

@yibin87 yibin87 commented Mar 11, 2026

What is changed, added or deleted? (Required)

  • Refresh dashboard/top-sql.md to match the current pingcap/tidb-dashboard master behavior.
  • Update the Top SQL doc to cover Top 5/20/100, CPU/Network/Logical IO ordering, TiKV By Query / By Table / By DB / By Region, and the enable/disable behavior for TiKV network IO collection.
  • Re-shoot and replace the Top SQL screenshots with the current UI, including the TiKV Order By Network and Order By Logical IO views.
  • Add two new screenshots to explicitly show the Order By dropdown and the Top SQL settings drawer for enabling TiKV Network IO collection.

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot bot added missing-translation-status This PR does not have translation status info. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 11, 2026
@yibin87
Copy link
Copy Markdown
Contributor Author

yibin87 commented Mar 11, 2026

/cc @zhaoshangzi

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 11, 2026

@yibin87: GitHub didn't allow me to request PR reviews from the following users: zhaoshangzi.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @zhaoshangzi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@yibin87 yibin87 requested review from hfxsd and nolouch March 11, 2026 09:19
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 11, 2026

@nolouch: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@hfxsd hfxsd added the needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. label Mar 12, 2026
@hfxsd hfxsd added translation/doing This PR’s assignee is translating this PR. and removed missing-translation-status This PR does not have translation status info. labels Mar 12, 2026
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 12, 2026

@zhaoshangzi: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Signed-off-by: yibin87 <huyibin@pingcap.com>
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 12, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from qiancai. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Mar 12, 2026

@zhaoshangzi: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@qiancai qiancai changed the title dashboard: refresh Top SQL docs and screenshots refresh TopSQL docs and screenshots Mar 30, 2026
@qiancai qiancai added translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. and removed translation/doing This PR’s assignee is translating this PR. labels Mar 30, 2026
@Oreoxmt
Copy link
Copy Markdown
Collaborator

Oreoxmt commented Apr 3, 2026

/cc @Oreoxmt

@ti-chi-bot ti-chi-bot bot requested a review from Oreoxmt April 3, 2026 03:48
---
title: TiDB Dashboard Top SQL 页面
summary: 使用 Top SQL 找到 CPU 开销较大的 SQL 语句
summary: 使用 Top SQL 找到消耗 CPU、网络和逻辑 IO 资源较多的查询
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
summary: 使用 Top SQL 找到消耗 CPU、网络和逻辑 IO 资源较多的查询
summary: 使用 Top SQL 找到消耗 CPU、网络和逻辑 I/O 资源较多的查询

* 通过图表及表格,可视化地展示 CPU 开销最多的 5 类 SQL 语句。
* 展示每秒请求数、平均延迟、查询计划等详细执行信息。
* 通过图表和表格展示当前时间范围内资源消耗最高的 Top `5`、`20` 或 `100` 类 SQL 查询,其余记录自动汇总为 `Others`。
* 支持按 CPU 耗时、网络字节数排序查看资源消耗热点;选择 TiKV 节点时,还支持按逻辑 IO 字节数排序。
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 支持按 CPU 耗时、网络字节数排序查看资源消耗热点;选择 TiKV 节点时,还支持按逻辑 IO 字节数排序。
* 支持按 CPU 耗时、网络字节数排序查看资源消耗热点;选择 TiKV 节点时,还支持按逻辑 I/O 字节数排序。

* 通过监控发现个别 TiDB 或 TiKV 节点 CPU 负载很高,希望快速定位是哪类 SQL 正在消耗大量 CPU 资源
* 集群整体查询变慢,希望找出当前最消耗资源的 SQL,或者对比负载变化前后最主要的查询差异
* 需要从更高维度定位热点,希望按 `Table`、`DB` 或 `Region` 聚合查看 TiKV 侧的资源消耗
* 需要从网络流量或逻辑 IO 角度排查 TiKV 热点,而不仅仅局限于 CPU 维度
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 需要从网络流量或逻辑 IO 角度排查 TiKV 热点,而不仅仅局限于 CPU 维度。
* 需要从网络流量或逻辑 I/O 角度排查 TiKV 热点,而不仅仅局限于 CPU 维度。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants