pingcap/tidb

UCP: Persist statement summary tables on disk

Open

#14,888 opened on 2020年2月21日

GitHub で見る
 (0 comments) (0 reactions) (0 assignees)Go (40,090 stars) (6,186 forks)batch import
component/infoschemahelp wantedtype/enhancement

説明

Description

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

Statement summary tables are memory tables and only provide performance data over recent hours. But in productive environment, we need to query earlier performance data and the data before the server restarts.

Describe the feature you'd like:

Persist statement summary tables on disk periodically. The save interval can't be too short, otherwise it will impact performance.

Describe alternatives you've considered:

  • Provide a tool to extract the data and save it on other places. It's not good because it complicate deployment.
  • Save the data on disks in TiDB server. It's not good because we need to define a customized format.

Score

  • 2996

Mentor

  • @djshow832

Contact the mentors: #tidb-challenge-program channel in TiDB Community Slack Workspace

Recommended Skills

  • Golang programming
  • SQL executor
  • TiDB DDL
  • TiKV Storage
  • MySQL performance schema

Learning Materials

コントリビューターガイド

技術スタック
gosql
領域
database
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
5
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Golang programmingSQL executorTiDB DDLTiKV Storage
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
15
調査方針
Study the current implementation of statement summary tables in TiDB, which are memory only. Review the TiDB documentation and code related to these tables. Investigate how other system tables are persisted in TiDB for patterns. Consider the alternatives listed in the issue and why they were rejected. Contact the mentor @djshow832 for further guidance. No existing PRs or discussion to build upon.