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!

MySQLoffersvariousstorageengines,eachsuitedfordifferentusecases:1)InnoDBisidealforapplicationsneedingACIDcomplianceandhighconcurrency,supportingtransactionsandforeignkeys.2)MyISAMisbestforread-heavyworkloads,lackingtransactionsupport.3)Memoryengineis

Common security vulnerabilities in MySQL include SQL injection, weak passwords, improper permission configuration, and unupdated software. 1. SQL injection can be prevented by using preprocessing statements. 2. Weak passwords can be avoided by forcibly using strong password strategies. 3. Improper permission configuration can be resolved through regular review and adjustment of user permissions. 4. Unupdated software can be patched by regularly checking and updating the MySQL version.

Identifying slow queries in MySQL can be achieved by enabling slow query logs and setting thresholds. 1. Enable slow query logs and set thresholds. 2. View and analyze slow query log files, and use tools such as mysqldumpslow or pt-query-digest for in-depth analysis. 3. Optimizing slow queries can be achieved through index optimization, query rewriting and avoiding the use of SELECT*.

To monitor the health and performance of MySQL servers, you should pay attention to system health, performance metrics and query execution. 1) Monitor system health: Use top, htop or SHOWGLOBALSTATUS commands to view CPU, memory, disk I/O and network activities. 2) Track performance indicators: monitor key indicators such as query number per second, average query time and cache hit rate. 3) Ensure query execution optimization: Enable slow query logs, record and optimize queries whose execution time exceeds the set threshold.

The main difference between MySQL and MariaDB is performance, functionality and license: 1. MySQL is developed by Oracle, and MariaDB is its fork. 2. MariaDB may perform better in high load environments. 3.MariaDB provides more storage engines and functions. 4.MySQL adopts a dual license, and MariaDB is completely open source. The existing infrastructure, performance requirements, functional requirements and license costs should be taken into account when choosing.

MySQL uses a GPL license. 1) The GPL license allows the free use, modification and distribution of MySQL, but the modified distribution must comply with GPL. 2) Commercial licenses can avoid public modifications and are suitable for commercial applications that require confidentiality.

The situations when choosing InnoDB instead of MyISAM include: 1) transaction support, 2) high concurrency environment, 3) high data consistency; conversely, the situation when choosing MyISAM includes: 1) mainly read operations, 2) no transaction support is required. InnoDB is suitable for applications that require high data consistency and transaction processing, such as e-commerce platforms, while MyISAM is suitable for read-intensive and transaction-free applications such as blog systems.

In MySQL, the function of foreign keys is to establish the relationship between tables and ensure the consistency and integrity of the data. Foreign keys maintain the effectiveness of data through reference integrity checks and cascading operations. Pay attention to performance optimization and avoid common errors when using them.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

Zend Studio 13.0.1
Powerful PHP integrated development environment

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

WebStorm Mac version
Useful JavaScript development tools
