Statistic Scope
Description
com_table_dump,
com_connect_out,
com_register_slave,
com_stmt_prepare,
com_stmt_execute,
com_stmt_send_long_data,
com_stmt_close,
com_stmt_reset,
com_stmt_set_option,
com_stmt_fetch,
com_daemon
Miscellaneous
Table 20.63. Returned mysqlnd statistics: Miscellaneous
Statistic Scope
Description
Process Total number of close prepared
explicit_stmt_close,
statements.
implicit_stmt_close
Process Memory management calls.
mem_emalloc_count,
mem_emalloc_ammount,
mem_ecalloc_count,
mem_ecalloc_ammount,
mem_erealloc_count,
mem_erealloc_ammount,
mem_efree_count,
mem_malloc_count,
mem_malloc_ammount,
mem_calloc_count,
mem_calloc_ammount,
mem_realloc_count,
mem_realloc_ammount,
mem_free_count
Connection N umber of network command buffer
command_buffer_too_small
extensions while sending commands
from PHP to MySQL.
MySQL Native Driver (Mysqlnd)
2543
Notes
• Calculate the average number of
prepared statement executions
by comparing
COM_EXECUTE
COM_PREPARE
• Check if PHP has run any non-
prepared SQL statements by
checking if
COM_QUERY
• Identify PHP scripts that run an
excessive number of SQL statements
by checking
COM_QUERY
COM_EXECUTE
Notes
A close is always considered explicit but
for a failed prepare.
Development only.
mysqlnd allocates an internal
command/network buffer of
mysqlnd.net_cmd_buffer_size
(php.ini) bytes for every connection.
If a MySQL Client Server protocol
command, for example,
(normal query), does not fit into the
buffer, mysqlnd will grow the buffer
to what is needed for sending the
command. Whenever the buffer
gets extended for one connection
command_buffer_too_small
incremented by one.
If mysqlnd has to grow the
buffer beyond its initial size of
mysqlnd.net_cmd_buffer_size
(php.ini) bytes for almost every
connection, you should consider to
increase the default size to avoid re-
allocations.
with
is zero
and
COM_QUERY
will be
Need help?
Do you have a question about the 5.0 and is the answer not in the manual?
Questions and answers