pingcap/tidb

Automatically troubleshooting SQL performance problems

Open

#14,892 opened on Feb 21, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (40,090 stars) (6,186 forks)batch import
component/infoschemahelp wantedtype/usability

Description

Feature Request

Is your feature request related to a problem? Please describe:

Now that we have statement summary tables, we can query these tables by ourselves when there's performance degression. But the metrics in these tables are too many to figure out the problem quickly.

Describe the feature you'd like:

We can define diagnosis rules to find the problems by TiDB server itself. For example, when TiDB notices that the average latency of one kind of SQL increases sharply in the last 30 minutes, the server can compare each metric between the latest summary with any history summary. And it can figure out the problem, say, locking contention, execution plan changing. Once it figures out these problems, it can output it to a performance view, or a report.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Contributor guide

Tech stack
gosqlmysql
Domain
databaseperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingSQL knowledgeTiDB internalsPerformance analysis
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate TiDB's statement summary tables and diagnose rules. Propose a design for automatic detection and reporting of SQL performance problems, including metrics comparison and rule definitions. Look at existing performance views and summary table structures.