[Yandex Cloud documentation](../index.md) > [Yandex MPP Analytics for PostgreSQL](index.md) > Inspections and recommendations

# Inspections and recommendations in Yandex MPP Analytics for PostgreSQL 

Managed database clusters regularly undergo diagnostics to detect possible issues, increase the cluster's reliability, and improve its performance. The results of such checks are displayed as inspections under **Recommendations**. You can see notifications about successful checks and recommendations on eliminating discovered risks. The responsibility to troubleshoot any detected issues lies within the Yandex Cloud user's [remit](../overview/concepts/mdb-responsibilities.md).

All checks have a severity level:

* High level: Criteria of high cluster availability, significant risks of reduced performance, data loss risks. Such checks warrant special attention and require following the recommendations provided. 
* Moderate level: Possible risks of reduced performance, suboptimal memory and disk space usage.
* Low level: Potential risks and cluster operation limitations.

The list of recommendations is updated regularly. For each recommendation, the following timestamps are fixed: the date of the risk's first detection and the date of the most recent status update on this issue. If the recommendation seems to be excessive or incorrect, you can hide it, specifying a reason. Once the hiding period expires, the recommendation will automatically become available again if the issue persists.

Recommendations are available at the cluster, folder, and cloud levels and provide tips for all your resources. However, the absence of recommendations does not mean that your cluster is optimized: the list of checks gets continuously appended but still remains incomprehensive and cannot replace monitoring, since it is **targeted at detecting patterns rather than specific issues**. You can additionally run cluster performance diagnostics and analyze monitoring metrics.

To manage recommendations in Yandex MPP Analytics for PostgreSQL, you need the [managed-greenplum.editor role or higher](security/index.md).

## Inspections available in Yandex MPP Analytics for PostgreSQL {#mgp-recommendations}

| **Category** | **Check** | **Risk** | **Severity** |
|---------------------|-------------------------|----------------------------------------------------------------------------------------------------|-----------------|
| Performance | CPU usage | [Risk of degraded performance](#greenplum_cpu_idle) | High         |
| High availability | Memory allocation | [Lack of RAM](#greenplum_oom) | Moderate       |
| High availability | ZSTD memory accounting | [Risk of exceeding resource manager memory limits](#greenplum_gp_enable_zstd_memory_accounting) | Moderate       |

### Risk of reduced performance {#greenplum_cpu_idle}

**Description**

The host continuously uses all CPU resources, which may cause delays in query processing. Check the [load](operations/monitoring.md) and optimize your queries (which may include using the WebSQL [AI assistant](../websql/operations/ai-assistant.md)) or increase computing resources of the cluster.

**Action**

To increase the cluster's computing resources:

1. Navigate to **Yandex MPP Analytics for PostgreSQL**.
1. Select your cluster and click ![image](../_assets/console-icons/pencil.svg) **Edit**.
1. Under **Resources**, select a host class with the required amount of vCPUs.
1. Click **Save changes**.

### Not enough RAM {#greenplum_oom}

**Description**

The cluster is running out of RAM, which leads to slow performance or emergency shutdowns. Increase the cluster's RAM.

**Action**

To increase the amount of RAM:

1. Navigate to **Yandex MPP Analytics for PostgreSQL**.
1. Select your cluster and click ![image](../_assets/console-icons/pencil.svg) **Edit**.
1. Under **Resources**, select a host class with the required amount of RAM.
1. Click **Save changes**. 

### Risk of exceeding resource manager memory limits {#greenplum_gp_enable_zstd_memory_accounting}

**Description**

The `gp_enable_zstd_memory_accounting` parameter controls memory allocation for the ZSTD algorithm. Enabling it prevents the system from exceeding the resource manager memory limits by allocating ZSTD to a separate `zstd_context`, which significantly reduces the risk of cluster failure due to OOM. We recommend enabling this parameter.

**Action**

To enable the `gp_enable_zstd_memory_accounting` parameter:

1. Navigate to **Yandex MPP Analytics for PostgreSQL**.
1. Select your cluster and click ![image](../_assets/console-icons/pencil.svg) **Edit**.
1. Click **Settings** under **DBMS settings** and enable `gp_enable_zstd_memory_accounting`.