Before there was
PERFORMANCE_SCHEMA, there was
SHOW ENGINE INNODB MUTEX. As I wrote yesterday, these commands are useful for exposing internal locking operations that happen inside of MySQL. They are mainly useful for MySQL developers, but have some appeal for DBAs as well.
As part of an ongoing effort to cleanup the MySQL code-base and increase usability, the MySQL development team is interested in hearing feedback from users who currently use the command
SHOW ENGINE INNODB MUTEX.
- Is there a use case for the command that is not well satisfied by Performance Schema?
- Would you be adversely affected if
SHOW ENGINE INNODB MUTEXwere to be deprecated?
- What tools do you use to analyze mutex contention, and what features could we add to benefit you?
Please leave a comment, or get in touch. We would love to hear from you.