Rechercher dans le manuel MySQL
26.4.8 Example Consumer Configurations
The consumer settings in the
setup_consumers
table form a
hierarchy from higher levels to lower. The following discussion
describes how consumers work, showing specific configurations
and their effects as consumer settings are enabled progressively
from high to low. The consumer values shown are representative.
The general principles described here apply to other consumer
values that may be available.
The configuration descriptions occur in order of increasing functionality and overhead. If you do not need the information provided by enabling lower-level settings, disable them and the Performance Schema will execute less code on your behalf and you will have less information to sift through.
The setup_consumers
table contains
the following hierarchy of values:
global_instrumentation
thread_instrumentation
events_waits_current
events_waits_history
events_waits_history_long
events_stages_current
events_stages_history
events_stages_history_long
events_statements_current
events_statements_history
events_statements_history_long
events_transactions_current
events_transactions_history
events_transactions_history_long
statements_digest
In the consumer hierarchy, the consumers for waits, stages, statements, and transactions are all at the same level. This differs from the event nesting hierarchy, for which wait events nest within stage events, which nest within statement events, which nest within transaction events.
If a given consumer setting is NO
, the
Performance Schema disables the instrumentation associated with
the consumer and ignores all lower-level settings. If a given
setting is YES
, the Performance Schema
enables the instrumentation associated with it and checks the
settings at the next lowest level. For a description of the
rules for each consumer, see
Section 26.4.7, “Pre-Filtering by Consumer”.
For example, if global_instrumentation
is
enabled, thread_instrumentation
is checked.
If thread_instrumentation
is enabled, the
events_
consumers are checked. If of these
xxx
_currentevents_waits_current
is enabled,
events_waits_history
and
events_waits_history_long
are checked.
Each of the following configuration descriptions indicates which setup elements the Performance Schema checks and which output tables it maintains (that is, for which tables it collects information).
No Instrumentation
Server configuration state:
- +---------------------------+---------+
- | NAME | ENABLED |
- +---------------------------+---------+
- ...
- +---------------------------+---------+
In this configuration, nothing is instrumented.
Setup elements checked:
Table
setup_consumers
, consumerglobal_instrumentation
Output tables maintained:
None
Server configuration state:
- +---------------------------+---------+
- | NAME | ENABLED |
- +---------------------------+---------+
- | global_instrumentation | YES |
- ...
- +---------------------------+---------+
In this configuration, instrumentation is maintained only for global states. Per-thread instrumentation is disabled.
Additional setup elements checked, relative to the preceding configuration:
Table
setup_consumers
, consumerthread_instrumentation
Table
setup_instruments
Table
setup_objects
Additional output tables maintained, relative to the preceding configuration:
Server configuration state:
- +----------------------------------+---------+
- | NAME | ENABLED |
- +----------------------------------+---------+
- | global_instrumentation | YES |
- | thread_instrumentation | YES |
- ...
- ...
- ...
- ...
- +----------------------------------+---------+
In this configuration, instrumentation is maintained globally and per thread. No individual events are collected in the current-events or event-history tables.
Additional setup elements checked, relative to the preceding configuration:
Table
setup_consumers
, consumersevents_
, wherexxx
_currentxxx
iswaits
,stages
,statements
,transactions
Table
setup_actors
Column
threads.instrumented
Additional output tables maintained, relative to the preceding configuration:
events_
, wherexxx
_summary_by_yyy
_by_event_namexxx
iswaits
,stages
,statements
,transactions
; andyyy
isthread
,user
,host
,account
Server configuration state:
- +----------------------------------+---------+
- | NAME | ENABLED |
- +----------------------------------+---------+
- | global_instrumentation | YES |
- | thread_instrumentation | YES |
- | events_waits_current | YES |
- | events_stages_current | YES |
- | events_statements_current | YES |
- | events_transactions_current | YES |
- ...
- +----------------------------------+---------+
In this configuration, instrumentation is maintained globally and per thread. Individual events are collected in the current-events table, but not in the event-history tables.
Additional setup elements checked, relative to the preceding configuration:
Consumers
events_
, wherexxx
_historyxxx
iswaits
,stages
,statements
,transactions
Consumers
events_
, wherexxx
_history_longxxx
iswaits
,stages
,statements
,transactions
Additional output tables maintained, relative to the preceding configuration:
events_
, wherexxx
_currentxxx
iswaits
,stages
,statements
,transactions
The preceding configuration collects no event history because
the
events_
and
xxx
_historyevents_
consumers are disabled. Those consumers can be enabled
separately or together to collect event history per thread,
globally, or both.
xxx
_history_long
This configuration collects event history per thread, but not globally:
- +----------------------------------+---------+
- | NAME | ENABLED |
- +----------------------------------+---------+
- | global_instrumentation | YES |
- | thread_instrumentation | YES |
- | events_waits_current | YES |
- | events_waits_history | YES |
- | events_stages_current | YES |
- | events_stages_history | YES |
- | events_statements_current | YES |
- | events_statements_history | YES |
- | events_transactions_current | YES |
- | events_transactions_history | YES |
- ...
- +----------------------------------+---------+
Event-history tables maintained for this configuration:
events_
, wherexxx
_historyxxx
iswaits
,stages
,statements
,transactions
This configuration collects event history globally, but not per thread:
- +----------------------------------+---------+
- | NAME | ENABLED |
- +----------------------------------+---------+
- | global_instrumentation | YES |
- | thread_instrumentation | YES |
- | events_waits_current | YES |
- | events_waits_history_long | YES |
- | events_stages_current | YES |
- | events_stages_history_long | YES |
- | events_statements_current | YES |
- | events_statements_history_long | YES |
- | events_transactions_current | YES |
- | events_transactions_history_long | YES |
- ...
- +----------------------------------+---------+
Event-history tables maintained for this configuration:
events_
, wherexxx
_history_longxxx
iswaits
,stages
,statements
,transactions
This configuration collects event history per thread and globally:
- +----------------------------------+---------+
- | NAME | ENABLED |
- +----------------------------------+---------+
- | global_instrumentation | YES |
- | thread_instrumentation | YES |
- | events_waits_current | YES |
- | events_waits_history | YES |
- | events_waits_history_long | YES |
- | events_stages_current | YES |
- | events_stages_history | YES |
- | events_stages_history_long | YES |
- | events_statements_current | YES |
- | events_statements_history | YES |
- | events_statements_history_long | YES |
- | events_transactions_current | YES |
- | events_transactions_history | YES |
- | events_transactions_history_long | YES |
- ...
- +----------------------------------+---------+
Event-history tables maintained for this configuration:
events_
, wherexxx
_historyxxx
iswaits
,stages
,statements
,transactions
events_
, wherexxx
_history_longxxx
iswaits
,stages
,statements
,transactions
Traduction non disponible
Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-performance-schema-consumer-configurations.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.