Rechercher dans le manuel MySQL
13.7.6.30 SHOW PROFILE Syntax
- [FOR QUERY n]
- type: {
- | BLOCK IO
- | CONTEXT SWITCHES
- | CPU
- | IPC
- | MEMORY
- | PAGE FAULTS
- | SOURCE
- | SWAPS
- }
The SHOW PROFILE
and
SHOW PROFILES
statements display
profiling information that indicates resource usage for
statements executed during the course of the current session.
The SHOW PROFILE
and
SHOW PROFILES
statements are
deprecated and will be removed in a future MySQL release. Use
the Performance
Schema instead; see
Section 26.19.1, “Query Profiling Using Performance Schema”.
To control profiling, use the
profiling
session variable,
which has a default value of 0 (OFF
). Enable
profiling by setting profiling
to 1 or ON
:
SHOW PROFILES
displays a list of
the most recent statements sent to the server. The size of the
list is controlled by the
profiling_history_size
session
variable, which has a default value of 15. The maximum value is
100. Setting the value to 0 has the practical effect of
disabling profiling.
All statements are profiled except SHOW
PROFILE
and SHOW
PROFILES
, so you will find neither of those statements
in the profile list. Malformed statements are profiled. For
example, SHOW PROFILING
is an illegal
statement, and a syntax error occurs if you try to execute it,
but it will show up in the profiling list.
SHOW PROFILE
displays detailed
information about a single statement. Without the FOR
QUERY
clause, the output
pertains to the most recently executed statement. If
n
FOR QUERY
is
included, n
SHOW PROFILE
displays
information for statement n
. The
values of n
correspond to the
Query_ID
values displayed by
SHOW PROFILES
.
The LIMIT
clause may be
given to limit the output to
row_count
row_count
rows. If
LIMIT
is given, OFFSET
may be added to
begin the output offset
offset
rows into the
full set of rows.
By default, SHOW PROFILE
displays
Status
and Duration
columns. The Status
values are like the
State
values displayed by
SHOW PROCESSLIST
, although there
might be some minor differences in interpretion for the two
statements for some status values (see
Section 8.14, “Examining Thread Information”).
Optional type
values may be specified
to display specific additional types of information:
ALL
displays all informationBLOCK IO
displays counts for block input and output operationsCONTEXT SWITCHES
displays counts for voluntary and involuntary context switchesCPU
displays user and system CPU usage timesIPC
displays counts for messages sent and receivedMEMORY
is not currently implementedPAGE FAULTS
displays counts for major and minor page faultsSOURCE
displays the names of functions from the source code, together with the name and line number of the file in which the function occursSWAPS
displays swap counts
Profiling is enabled per session. When a session ends, its profiling information is lost.
- +-------------+
- | @@profiling |
- +-------------+
- | 0 |
- +-------------+
- Query OK, 0 rows affected (0.00 sec)
- Query OK, 0 rows affected, 1 warning (0.00 sec)
- Query OK, 0 rows affected (0.01 sec)
- +----------+----------+--------------------------+
- | Query_ID | Duration | Query |
- +----------+----------+--------------------------+
- +----------+----------+--------------------------+
- +----------------------+----------+
- +----------------------+----------+
- | checking permissions | 0.000040 |
- | freeing items | 0.000089 |
- | logging slow query | 0.000019 |
- | cleaning up | 0.000005 |
- +----------------------+----------+
- +--------------------+----------+
- +--------------------+----------+
- | freeing items | 0.000008 |
- | logging slow query | 0.000015 |
- | cleaning up | 0.000006 |
- +--------------------+----------+
- +----------------------+----------+----------+------------+
- +----------------------+----------+----------+------------+
- | checking permissions | 0.000040 | 0.000038 | 0.000002 |
- | freeing items | 0.000089 | 0.000010 | 0.000014 |
- | logging slow query | 0.000019 | 0.000009 | 0.000010 |
- | cleaning up | 0.000005 | 0.000003 | 0.000002 |
- +----------------------+----------+----------+------------+
Profiling is only partially functional on some architectures.
For values that depend on the getrusage()
system call, NULL
is returned on systems
such as Windows that do not support the call. In addition,
profiling is per process and not per thread. This means that
activity on threads within the server other than your own may
affect the timing information that you see.
Profiling information is also available from the
INFORMATION_SCHEMA
PROFILING
table. See
Section 25.19, “The INFORMATION_SCHEMA PROFILING Table”. For example, the following
queries are equivalent:
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-show-profile.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.