You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The workload repository will persist workload metrics for use by the planner and statistics systems. These data will be used by:
the Statistics Advisor, which will help determine statistics loading priorities,
the Index Advisor, which will make recommendations about indexes,
the SQL tuning and SQL binding advisor,
Select tables will be sampled by two different methods at regular intervals, and persist the results into the "workload_schema" database. Sampled tables are node-specific and each TiDB instance will sample and write these data independently.
Some tables will be sampled on an interval between 1 and 600 seconds.
The data from each of these tables will be sampled and recorded in the corresponding tables in 'workload_schema' along with the sampling timestamp and instance id. These tables include:
PROCESSLIST
DATA_LOCK_WAITS
TIDB_TRX MEMORY_USAGE
DEADLOCKS CLUSTER_LOAD
TIDB_HOT_REGIONS
TIKV_STORE_STATUS
Other tables will be sampled as part of a snapshot process, which will run every 15 minutes to 2 hours. When a snapshot is initialized, one row will be written into HIST_SNAPSHOTS, which will contain the snapshot id, the start and end timestamps, and server version information. The data from each of the following tables will be sampled and recorded in the corresponding tables in 'workload_schema' along with the sampling timestamp, instance id and snapshot id:
CLIENT_ERRORS_SUMMARY_BY_HOST
CLIENT_ERRORS_SUMMARY_BY_USER
CLIENT_ERRORS_SUMMARY_GLOBAL
TIKV_REGION_STATUS
TIDB_STATEMENTS_STATS
Other tables will probably be added to these lists.
The text was updated successfully, but these errors were encountered:
The workload repository will persist workload metrics for use by the planner and statistics systems. These data will be used by:
Select tables will be sampled by two different methods at regular intervals, and persist the results into the "workload_schema" database. Sampled tables are node-specific and each TiDB instance will sample and write these data independently.
Some tables will be sampled on an interval between 1 and 600 seconds.
The data from each of these tables will be sampled and recorded in the corresponding tables in 'workload_schema' along with the sampling timestamp and instance id. These tables include:
Other tables will be sampled as part of a snapshot process, which will run every 15 minutes to 2 hours. When a snapshot is initialized, one row will be written into HIST_SNAPSHOTS, which will contain the snapshot id, the start and end timestamps, and server version information. The data from each of the following tables will be sampled and recorded in the corresponding tables in 'workload_schema' along with the sampling timestamp, instance id and snapshot id:
Other tables will probably be added to these lists.
The text was updated successfully, but these errors were encountered: