Performance reporting controls in Mysql Workbench

The controls listed below can be used to inspect and export performance report data (see image below) -

• Export - Exports all entries in the current performance report, including all queries and values ​​and any associated data (including column headers). Opens the Export File dialog box.

• Copy Selection - Copies a single entry from the current performance report along with any related data (and column headers). System clipboard saved. A typical example

• Query Copy - This function copies the SQL statement that generates the performance report. System clipboard saved.

• Refresh - The performance report has been refreshed (reloaded).

Performance Report Instructions

Performance Report: Report Analysis

Display the following groupings for each report -

Memory usage

• Total Memory - Displays the total memory allocated.

• Highest Memory by Event - Shows the events that consume the most memory.

• Highest Memory by User - Shows the users consuming the most memory

• Highest Memory by Host - Shows the hosts consuming the most memory.

• Highest Memory by Thread - Shows the threads consuming the most memory.

I/O Hotspot

• Main File I/O Activity Report - Shows the files with the most I/O usage in bytes.

• Highest I/O for files by time - Shows top I/O usage by file and latency.

• Top I/O by Event Category - Displays the top I/O data usage by event category.

• Top I/O Time by Event Category - Displays the top I/O time consumers by event category.

• Top I/O by User/Thread - Shows the top I/O time consumers by user and thread.

High-cost SQL statements

• Statement Analysis - Lists statements with various aggregate statistics.

• Top 5% of statements running time - Lists all statements that are in the top 5% of average running times (in microseconds).

• Using Temporary Tables - Lists all statements that use temporary tables (accessing the highest percentage of disk temporary tables, followed by in-memory temporary tables).

• With Sorting - Lists all normalization statements that have completed sorting (accessed in the following order of precedence: sort_merge_passes, sort_scans, and sort_rows).

• Full table scan - Lists statements that have performed a full table scan. Access query performance and the WHERE clause (or clauses). If you are not using indexes, consider adding indexes to large tables.

• Errors or Warnings - Lists statements that raised errors or warnings.

Database Architecture Statistics

• Schema Object Overview (High Overhead) - Displays object count per schema. Note that this report may take longer to execute for instances with a large number of objects.

• Schema Index Statistics - Displays general statistics related to the index.

• Mode Table Statistics - Displays general statistics related to the table.

• Schema table statistics (with InnoDB buffers) - Displays schema tables with InnoDB buffer statistics.

• Tables with full table scans - Finds tables accessed via full table scans, sorted by the number of rows scanned (descending order).

• Unused Indexes - Displays a list of indexes that have never been used since the server started or P_S data collection began.

Waiting event time (expert)

• Global Waits by Time - Lists the most important global wait events by total time, ignoring idle (which may not be huge).

• Wait Time by User - Lists the most common wait events by user and their total time, ignoring idle (which is probably not huge).

• Wait classes by time - Lists the most important wait classes by total time, ignoring idle (which may not be huge).

• Wait classes by average time - Lists the most important wait classes by average time, ignoring idle (which may not be huge).

InnoDB Statistics

• InnoDB Buffer Stats by Schema - Summarizes the output of the INFORMATION_SCHEMA.INNODB_BUFFER_PAGE table, aggregated by schema.

• InnoDB Buffer Stats by Table - Summarizes output for the INFORMATION_SCHEMA.INNODB_BUFFER_PAGE table, aggregated by schema and table name.

User resource usage

• Overview - Displays a summary of resource usage for each user.

• I/O Statistics - Shows I/O usage per user.

• Statement Statistics - This displays statement execution statistics for each user.

in conclusion

In this article, we learned about the different performance reporting controls and how to obtain them using mysql Workbench.

The above is the detailed content of Performance reporting controls in Mysql Workbench. For more information, please follow other related articles on the PHP Chinese website!