Use INNODB_METRICS for extended XtraDB stats
Moved to https:/
There's some overlap between XtraDB extended status variables from http://
It makes sense to revise that list and check what stats can be removed or reimplemented as INNODB_METRICS counters. The benefits of INNODB_METRICS over status variables is ability to enable/disable counters selectively, retrospection, stopwatch-like time interval values, etc. The downside is a counter-intuitive configuration, see http://
Naturally, this should be implemented before the GA release, as changing the list of available status variables will be problematic afterwards.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Not
- Drafter:
- Alexey Kopytov
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- Accepted for 5.6
- Implementation:
-
Needs Infrastructure
- Milestone target:
- None
- Started by
- Laurynas Biveinis
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Implementing RO and RW trx list lengths in I_M tables belongs to this blueprint as well.
Waiting for some peformance numbers.
Current idea is not to remove the status vars (as they are already ported), and consider addding the I_M support on the top (InnoDB has provisions for that). Then I_M support decision needs not to happen before the GA.
Note also the deadlock count (bug 1192052).
