- 1 Performance Schema Quick Start
- 2 Performance Schema Configuration
- 3 Performance Schema Status Monitoring
- 4 Performance Schema Event Timing
- 5 Performance Schema Event Instrument Naming Conventions
- 6 Performance Schema Table General Characteristics
- 7 Performance Schema Table Descriptions
- 8 Performance Schema and Plugins
- 9 Performance Schema System Variables
- 10 Performance Schema Status Variables
- 11 Using Performance Schema to Diagnose Problems
- 12 Performance Schema Restrictions
- 13 Other Changes to Manual
[+/-]
The capabilities described in this document are currently under
development and are available in the source tree contained in the
mysql-next-mr BZR repository. To use
Performance Schema, you must create a branch (local copy) of this
repository.
Create a branch of the mysql-next-mr
repository. If you do not already have a BZR repository directory
created, initialize it using the instructions at
Installing from the Development Source Tree. To create a new branch,
use the following command:
shell> bzr branch lp:~mysql/mysql-server/mysql-next-mr mysql-next-mr
The command creates a local source tree in a directory named
mysql-next-mr. Use a different name for the
final argument if you like.
To use MySQL Performance Schema, these configuration considerations apply:
Performance Schema must be configured into MySQL Server at build time to make it available. See Section 2.1, “Performance Schema Build Configuration”.
Performance Schema must be enabled at server startup to enable event collection to occur. Specific Performance Schema features can be enabled at server startup or at runtime to control which types of event collection occur. See Section 2.3, “Event Collection Pre-Filtering and Post-Filtering”.
