refresh TopSQL docs and screenshots#21431
Conversation
|
/cc @zhaoshangzi |
|
@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. DetailsIn 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. |
|
@nolouch: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn 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. |
|
@zhaoshangzi: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn 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>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@zhaoshangzi: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn 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. |
|
/cc @Oreoxmt |
| --- | ||
| title: TiDB Dashboard Top SQL 页面 | ||
| summary: 使用 Top SQL 找到 CPU 开销较大的 SQL 语句 | ||
| summary: 使用 Top SQL 找到消耗 CPU、网络和逻辑 IO 资源较多的查询 |
There was a problem hiding this comment.
| summary: 使用 Top SQL 找到消耗 CPU、网络和逻辑 IO 资源较多的查询 | |
| summary: 使用 Top SQL 找到消耗 CPU、网络和逻辑 I/O 资源较多的查询。 |
| * 通过图表及表格,可视化地展示 CPU 开销最多的 5 类 SQL 语句。 | ||
| * 展示每秒请求数、平均延迟、查询计划等详细执行信息。 | ||
| * 通过图表和表格展示当前时间范围内资源消耗最高的 Top `5`、`20` 或 `100` 类 SQL 查询,其余记录自动汇总为 `Others`。 | ||
| * 支持按 CPU 耗时、网络字节数排序查看资源消耗热点;选择 TiKV 节点时,还支持按逻辑 IO 字节数排序。 |
There was a problem hiding this comment.
| * 支持按 CPU 耗时、网络字节数排序查看资源消耗热点;选择 TiKV 节点时,还支持按逻辑 IO 字节数排序。 | |
| * 支持按 CPU 耗时、网络字节数排序查看资源消耗热点;选择 TiKV 节点时,还支持按逻辑 I/O 字节数排序。 |
| * 通过监控发现个别 TiDB 或 TiKV 节点 CPU 负载很高,希望快速定位是哪类 SQL 正在消耗大量 CPU 资源。 | ||
| * 集群整体查询变慢,希望找出当前最消耗资源的 SQL,或者对比负载变化前后最主要的查询差异。 | ||
| * 需要从更高维度定位热点,希望按 `Table`、`DB` 或 `Region` 聚合查看 TiKV 侧的资源消耗。 | ||
| * 需要从网络流量或逻辑 IO 角度排查 TiKV 热点,而不仅仅局限于 CPU 维度。 |
There was a problem hiding this comment.
| * 需要从网络流量或逻辑 IO 角度排查 TiKV 热点,而不仅仅局限于 CPU 维度。 | |
| * 需要从网络流量或逻辑 I/O 角度排查 TiKV 热点,而不仅仅局限于 CPU 维度。 |
What is changed, added or deleted? (Required)
dashboard/top-sql.mdto match the currentpingcap/tidb-dashboardmaster behavior.By Query/By Table/By DB/By Region, and the enable/disable behavior for TiKV network IO collection.Order By NetworkandOrder By Logical IOviews.Order Bydropdown and the Top SQL settings drawer for enabling TiKV Network IO collection.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?