From b5c6366400282156c970c761fc342afce1ce7ea3 Mon Sep 17 00:00:00 2001 From: Hiroshi Yoshioka <40815708+hyoshioka0128@users.noreply.github.com> Date: Fri, 15 Nov 2024 00:40:53 +0900 Subject: [PATCH] =?UTF-8?q?Update=20how-to-troubleshoot-high-cpu-utilizati?= =?UTF-8?q?on.md=20(Typo=20"flexible=20server"=E2=86=92"Flexible=20Server"?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/how-to-troubleshoot-high-cpu-utilization.md #PingMSFTDocs --- .../how-to-troubleshoot-high-cpu-utilization.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/articles/mysql/flexible-server/how-to-troubleshoot-high-cpu-utilization.md b/articles/mysql/flexible-server/how-to-troubleshoot-high-cpu-utilization.md index 389395e569..2d6e27a24a 100644 --- a/articles/mysql/flexible-server/how-to-troubleshoot-high-cpu-utilization.md +++ b/articles/mysql/flexible-server/how-to-troubleshoot-high-cpu-utilization.md @@ -16,7 +16,7 @@ ms.topic: troubleshooting [!INCLUDE[azure-database-for-mysql-single-server-deprecation](~/reusable-content/ce-skilling/azure/includes/mysql/includes/azure-database-for-mysql-single-server-deprecation.md)] -Azure Database for MySQL flexible server provides a range of metrics that you can use to identify resource bottlenecks and performance issues on the server. To determine whether your server is experiencing high CPU utilization, monitor metrics such as “Host CPU percent”, “Total Connections”, “Host Memory Percent”, and “IO Percent”. At times, viewing a combination of these metrics will provide insights into what might be causing the increased CPU utilization on your Azure Database for MySQL flexible server instance. +Azure Database for MySQL Flexible Server provides a range of metrics that you can use to identify resource bottlenecks and performance issues on the server. To determine whether your server is experiencing high CPU utilization, monitor metrics such as “Host CPU percent”, “Total Connections”, “Host Memory Percent”, and “IO Percent”. At times, viewing a combination of these metrics will provide insights into what might be causing the increased CPU utilization on your Azure Database for MySQL Flexible Server instance. For example, consider a sudden surge in connections that initiates surge of database queries that cause CPU utilization to shoot up. @@ -50,7 +50,7 @@ Queries that are expensive to execute and scan a large number of rows without an ## Capturing details of the current workload -The SHOW (FULL) PROCESSLIST command displays a list of all user sessions currently connected to the Azure Database for MySQL flexible server instance. It also provides details about the current state and activity of each session. +The SHOW (FULL) PROCESSLIST command displays a list of all user sessions currently connected to the Azure Database for MySQL Flexible Server instance. It also provides details about the current state and activity of each session. This command only produces a snapshot of the current session status and doesn't provide information about historical session activity. @@ -150,7 +150,7 @@ This state usually means the open table operation is consuming a long time. Usua ### Sending data -While this state can mean that the thread is sending data through the network, it can also indicate that the query is reading data from the disk or memory. This state can be caused by a sequential table scan. You should check the values of the innodb_buffer_pool_reads and innodb_buffer_pool_read_requests to determine whether a large number of pages are being served from the disk into the memory. For more information, see [Troubleshoot low memory issues in Azure Database for MySQL flexible server](how-to-troubleshoot-low-memory-issues.md). +While this state can mean that the thread is sending data through the network, it can also indicate that the query is reading data from the disk or memory. This state can be caused by a sequential table scan. You should check the values of the innodb_buffer_pool_reads and innodb_buffer_pool_read_requests to determine whether a large number of pages are being served from the disk into the memory. For more information, see [Troubleshoot low memory issues in Azure Database for MySQL Flexible Server](how-to-troubleshoot-low-memory-issues.md). ### Updating