Muokkaa

Jaa

Troubleshoot high memory utilization in Azure Database for PostgreSQL - Flexible Server

  • Artikkeli

APPLIES TO: Azure Database for PostgreSQL - Flexible Server

This article describes how to identify the root cause of high memory utilization. It also provides possible remedial actions to control CPU utilization when using Azure Database for PostgreSQL Flexible Server.

In this article, you can learn:

  • About troubleshooting guides to identify and get recommendations to mitigate root causes.
  • About tools to identify high memory utilization.
  • Reasons for high memory utilization and remedial actions.

Troubleshooting guides

Using the Troubleshooting guides you can identify the probable root cause of a high CPU scenario, and can read through recommendations to mitigate the problem found.

To learn how to set up and use the troubleshooting guides, follow setup troubleshooting guides.

Tools to identify high memory utilization

Consider the use of the following list of tools to identify high CPU utilization.

Azure Metrics

Azure Metrics is a good starting point to monitor the percentage of memory in use for a specific period.

For proactive monitoring, you can configure alerts on the metrics. For step-by-step guidance, see Azure Metrics.

Query store

Query store automatically captures the history of queries and runtime statistics, and it retains them for your review. It slices the data by time, so that you can see temporal usage patterns. Data for all users, databases, and queries is stored in a database named azure_sys in the Azure Database for PostgreSQL flexible server instance.

Query store can correlate wait event information with query run time statistics. Use query store to identify queries that have high memory consumption during the period of interest.

For more information, see query store.

Reasons and remedial actions

Consider the following reasons and remedial actions for resolving high memory utilization.

Server parameters

An inappropriate configuration of the following server parameters could have an impact in the amount of memory consumed by your workload. Therefore, their values should be reviewed and adjusted according to your needs:

Use EXPLAIN ANALYZE

Once you know the queries that are consuming more memory, use EXPLAIN ANALYZE to further investigate and tune them.

For more information about the EXPLAIN ANALYZE command, review its documentation.

Share your suggestions and bugs with the Azure Database for PostgreSQL product team.

Related content