File I/O Summary Tables


The file I/O summary tables aggregate information about I/O operations:

For example:

mysql> SELECT * FROM file_summary_by_event_name\G
...
*************************** 2. row ***************************
 EVENT_NAME: wait/io/file/sql/binlog
 COUNT_STAR: 31
 SUM_TIMER_WAIT: 8243784888
 MIN_TIMER_WAIT: 0
 AVG_TIMER_WAIT: 265928484
 MAX_TIMER_WAIT: 6490658832
...
mysql> SELECT * FROM file_summary_by_instance\G
...
*************************** 2. row ***************************
 FILE_NAME: /var/mysql/share/english/errmsg.sys
 EVENT_NAME: wait/io/file/sql/ERRMSG
 EVENT_NAME: wait/io/file/sql/ERRMSG
 OBJECT_INSTANCE_BEGIN: 4686193384
 COUNT_STAR: 5
 SUM_TIMER_WAIT: 13990154448
 MIN_TIMER_WAIT: 26349624
 AVG_TIMER_WAIT: 2798030607
 MAX_TIMER_WAIT: 8150662536
...

TRUNCATE TABLE is permitted for summary tables. It resets the counters to zero rather than removing rows.

The file I/O summary tables have these grouping columns to indicate how events are aggregated:

The file I/O summary tables have the following summary columns containing aggregated values. (Before MariaDB 5.6.4, the tables contain only the Only COUNT_READ COUNT_WRITE SUM_NUMBER_OF_BYTES_READ, and SUM_NUMBER_OF_BYTES_WRITE aggregation columns.) Some columns are more general and have values that are the same as the sum of the values of more fine-grained columns. In this way, aggregations at higher levels are available directly without the need for user-defined views that sum lower-level columns.

Retornar