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 |
+-------------------------------------------+-------+For information on using these variables to check Performance Schema status, see *note performance-schema-status-monitoring::.
Performance Schema status variables have the following meanings:
'Performance_schema_accounts_lost'
The number of times a row could not be added to the *note 'accounts': performance-schema-accounts-table. table because it was full.
'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 *note 'events_statements_summary_by_digest': performance-schema-statement-summary-tables. table. This can be nonzero if the value of 'performance_schema_digests_size' is too small.
'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 *note 'hosts': performance-schema-hosts-table. table because it was full.
'Performance_schema_index_stat_lost'
The number of indexes for which statistics were lost. This can be nonzero if the value of 'performance_schema_max_index_stat' is too small.
'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_memory_classes_lost'
The number of times a memory instrument could not be loaded.
'Performance_schema_metadata_lock_lost'
The number of metadata locks that could not be instrumented in the *note 'metadata_locks': performance-schema-metadata-locks-table. table. This can be nonzero if the value of 'performance_schema_max_metadata_locks' is too small.
'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_nested_statement_lost'
The number of stored program statements for which statistics were lost. This can be nonzero if the value of 'performance_schema_max_statement_stack' is too small.
'Performance_schema_prepared_statements_lost'
The number of prepared statements that could not be instrumented in the *note 'prepared_statements_instances': performance-schema-prepared-statements-instances-table. table. This can be nonzero if the value of 'performance_schema_max_prepared_statements_instances' is too small.
'Performance_schema_program_lost'
The number of stored programs for which statistics were lost. This can be nonzero if the value of 'performance_schema_max_program_instances' is too small.
'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 connections for which connection attribute truncation has occurred. For a given connection, if the client sends connection attribute key-value pairs for which the aggregate size is larger than the reserved storage permitted by the value of the 'performance_schema_session_connect_attrs_size' system variable, the Performance Schema truncates the attribute data and increments 'Performance_schema_session_connect_attrs_lost'. If this value is nonzero, you may wish to set 'performance_schema_session_connect_attrs_size' to a larger value.
For more information about connection attributes, see *note performance-schema-connection-attribute-tables::.
'Performance_schema_socket_classes_lost'
How many socket instruments could not be loaded.
'Performance_schema_socket_instances_lost'
How many socket instrument instances could not be created.
'Performance_schema_stage_classes_lost'
How many stage instruments could not be loaded.
'Performance_schema_statement_classes_lost'
How many statement instruments could not be loaded.
'Performance_schema_table_handles_lost'
How many table instrument instances could not be opened. This can be nonzero if the value of 'performance_schema_max_table_handles' is too small.
'Performance_schema_table_instances_lost'
How many table instrument instances could not be created.
'Performance_schema_table_lock_stat_lost'
The number of tables for which lock statistics were lost. This can be nonzero if the value of 'performance_schema_max_table_lock_stat' is too small.
'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 *note 'threads': performance-schema-threads-table. 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 *note 'users': performance-schema-users-table. table because it was full.
File: manual.info.tmp, Node: performance-schema-memory-model, Next: performance-schema-and-plugins, Prev: performance-schema-status-variables, Up: performance-schema