pingcap/tidb

Automatically troubleshooting SQL performance problems

Open

#14.892 aperta il 21 feb 2020

Vedi su GitHub
 (0 commenti) (0 reazioni) (0 assegnatari)Go (6186 fork)batch import
component/infoschemahelp wantedtype/usability

Metriche repository

Star
 (40.090 star)
Metriche merge PR
 (Merge medio 14g 4h) (346 PR mergiate in 30 g)

Descrizione

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:

Guida contributor