Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
Description
The InnoDB monitor was a precursor of PERFORMANCE_SCHEMA in InnoDB, added in MySQL 5.5.
There should be only one (good) performance monitoring mechanism. Now we have several:
- SHOW ENGINE INNODB STATUS (hopefully to be removed at some part of future)
- INFORMATION_SCHEMA.GLOBAL_STATUS
- INFORMATION_SCHEMA.INNODB_METRICS (to be removed in this task)
- PERFORMANCE_SCHEMA
We should evaluate all the INNODB_METRICS counters and construct a mapping to the PERFORMANCE_SCHEMA or GLOBAL_STATUS counters correspond to them. There may be some obscure counters that can be removed; also these must be documented. Some counters may need to be added to PERFORMANCE_SCHEMA or GLOBAL_STATUS. If updating some status is not expensive, we might as well update it all the time and expose via GLOBAL_STATUS.
Attachments
Issue Links
- is blocked by
-
MDEV-17732 Write functional tests for the InnoDB monitor counters in information_schema.innodb_metrics
- Confirmed
- relates to
-
MDEV-9077 bundle sys schema
- Closed
-
MDEV-11384 AliSQL: [Feature] Issue#19 BUFFER POOL LIST SCAN OPTIMIZATION
- Closed
-
MDEV-16580 Remove unused monitor counters from InnoDB
- Closed
-
MDEV-17306 rw_lock_x_lock_wait_func() double increments rw_x_spin_round_count
- Closed
-
MDEV-21452 Use condition variables and normal mutexes instead of InnoDB os_event and mutex
- Closed
-
MDEV-22858 Remove unused innodb_mem_validate_usec, innodb_master_purge_usec
- Closed
-
MDEV-25687 trx_active_transactions is inconsistent and a potential performance hog; remove it
- Closed
-
MDEV-25689 metadata_table_reference_count, metadata_table_handles_closed are updated inconsistently; remove them
- Closed
-
MDEV-31308 InnoDB monitor trx_rseg_history_len was accidentally disabled by default
- Closed
-
MDEV-17441 InnoDB transition to C++11 atomics
- Closed