Documentation Home
MySQL 5.6 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 30.6Mb
PDF (A4) - 30.8Mb
PDF (RPM) - 30.1Mb
EPUB - 7.7Mb
HTML Download (TGZ) - 7.5Mb
HTML Download (Zip) - 7.5Mb
HTML Download (RPM) - 6.4Mb
Eclipse Doc Plugin (TGZ) - 8.2Mb
Eclipse Doc Plugin (Zip) - 10.1Mb
Man Pages (TGZ) - 200.2Kb
Man Pages (Zip) - 311.6Kb
Info (Gzip) - 2.9Mb
Info (Zip) - 2.9Mb
Excerpts from this Manual

MySQL 5.6 Reference Manual  /  MySQL Performance Schema  /  Performance Schema Status Variables

22.13 Performance Schema Status Variables

The Performance Schema implements several status variables that provide information about instrumentation that could not be loaded or created due to memory constraints:

mysql> SHOW STATUS LIKE 'perf%';
+-------------------------------------------+-------+
| Variable_name                             | Value |
+-------------------------------------------+-------+
| Performance_schema_accounts_lost          | 0     |
| Performance_schema_cond_classes_lost      | 0     |
| Performance_schema_cond_instances_lost    | 0     |
| Performance_schema_file_classes_lost      | 0     |
| Performance_schema_file_handles_lost      | 0     |
| Performance_schema_file_instances_lost    | 0     |
| Performance_schema_hosts_lost             | 0     |
| Performance_schema_locker_lost            | 0     |
| Performance_schema_mutex_classes_lost     | 0     |
| Performance_schema_mutex_instances_lost   | 0     |
| Performance_schema_rwlock_classes_lost    | 0     |
| Performance_schema_rwlock_instances_lost  | 0     |
| Performance_schema_socket_classes_lost    | 0     |
| Performance_schema_socket_instances_lost  | 0     |
| Performance_schema_stage_classes_lost     | 0     |
| Performance_schema_statement_classes_lost | 0     |
| Performance_schema_table_handles_lost     | 0     |
| Performance_schema_table_instances_lost   | 0     |
| Performance_schema_thread_classes_lost    | 0     |
| Performance_schema_thread_instances_lost  | 0     |
| Performance_schema_users_lost             | 0     |
+-------------------------------------------+-------+

Performance Schema status variables have the following meanings:

  • Performance_schema_accounts_lost

    The number of times a row could not be added to the accounts table because it was full. This variable was added in MySQL 5.6.3.

  • Performance_schema_cond_classes_lost

    How many condition instruments could not be loaded.

  • Performance_schema_cond_instances_lost

    How many condition instrument instances could not be created.

  • Performance_schema_digest_lost

    The number of digest instances that could not be instrumented in the events_statements_summary_by_digest table. This can be nonzero if the value of performance_schema_digests_size is too small. This variable was added in MySQL 5.6.5.

  • Performance_schema_file_classes_lost

    How many file instruments could not be loaded.

  • Performance_schema_file_handles_lost

    How many file instrument instances could not be opened.

  • Performance_schema_file_instances_lost

    How many file instrument instances could not be created.

  • Performance_schema_hosts_lost

    The number of times a row could not be added to the hosts table because it was full. This variable was added in MySQL 5.6.3.

  • Performance_schema_locker_lost

    How many events are lost or not recorded, due to the following conditions:

    • Events are recursive (for example, waiting for A caused a wait on B, which caused a wait on C).

    • The depth of the nested events stack is greater than the limit imposed by the implementation.

    Events recorded by the Performance Schema are not recursive, so this variable should always be 0.

  • Performance_schema_mutex_classes_lost

    How many mutex instruments could not be loaded.

  • Performance_schema_mutex_instances_lost

    How many mutex instrument instances could not be created.

  • Performance_schema_rwlock_classes_lost

    How many rwlock instruments could not be loaded.

  • Performance_schema_rwlock_instances_lost

    How many rwlock instrument instances could not be created.

  • Performance_schema_session_connect_attrs_lost

    The number of times a connection attribute string was larger than the reserved storage. This variable was added in MySQL 5.6.7.

  • Performance_schema_socket_classes_lost

    How many socket instruments could not be loaded. This variable was added in MySQL 5.6.3.

  • Performance_schema_socket_instances_lost

    How many socket instrument instances could not be created. This variable was added in MySQL 5.6.3.

  • Performance_schema_stage_classes_lost

    How many stage instruments could not be loaded. This variable was added in MySQL 5.6.3.

  • Performance_schema_statement_classes_lost

    How many statement instruments could not be loaded. This variable was added in MySQL 5.6.3.

  • Performance_schema_table_handles_lost

    How many table instrument instances could not be opened.

  • Performance_schema_table_instances_lost

    How many table instrument instances could not be created.

  • Performance_schema_thread_classes_lost

    How many thread instruments could not be loaded.

  • Performance_schema_thread_instances_lost

    The number of thread instances that could not be instrumented in the threads table. This can be nonzero if the value of performance_schema_max_thread_instances is too small.

  • Performance_schema_users_lost

    The number of times a row could not be added to the users table because it was full. This variable was added in MySQL 5.6.3.

For information on using these variables to check Performance Schema status, see Section 22.5, “Performance Schema Status Monitoring”.


User Comments
Sign Up Login You must be logged in to post a comment.