Please check the Query Performance Insight which is designed to help you spend less time troubleshooting database performance by providing such information as:
- Top N long-running queries and their trends.
- The query details: view the history of execution with minimum, maximum, average, and standard deviation query time.
- The resource utilizations (CPU, memory, and storage).
In Query Performance Insight, two metrics that can help you find potential bottlenecks are duration and execution count. Long-running queries have the greatest potential for locking resources longer, blocking other users, and limiting scalability.
You can also Configure slow query logs by using the Azure portal- In the server parameters you may need to select ON for slow_query_log parameter Here is reference document https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-slow-query-logs#configure-slow-query-logging
You can also try upscaling an instance if that make any difference and later downscale.
In some cases, a high execution count can lead to more network round trips. Round trips affect performance. So execution count can help to find frequently executed ("chatty") queries. These queries are the best candidates for optimization.
Thank You!