> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2026.2/server-update-and-maintenance/troubleshooting/performance-issues.md).

# Performance issues

In case of performance issues, you may try the following:

* Review the [Server host requirements](/sonarqube-server/2026.2/server-installation/server-host-requirements.md) for SonarQube Server linked to **Elasticsearch** usage.
* Move the Elasticsearch storage to a storage with high IOPS and low latency. See [Basic installation](/sonarqube-server/2026.2/server-installation/from-zip-file/basic-installation.md#configure-es-storage-path) for more information.
* Set the [Housekeeping](/sonarqube-server/2026.2/instance-administration/system-functions/housekeeping.md) with a reduced retention time, to limit the database size.
* Configure the analysis scope to reduce the number of files analyzed, leading to shorter analysis and smaller database footprint. See [Introduction](/sonarqube-server/2026.2/project-administration/adjusting-analysis/setting-analysis-scope/introduction.md) for more information.
* From the [Enterprise Edition](https://www.sonarsource.com/plans-and-pricing/enterprise/): increase the number of Compute Engine workers and/or configure the Compute Engine to enable parallel processing of pull requests and branch analyses for each project. See [Improving performance](/sonarqube-server/2026.2/server-update-and-maintenance/maintenance/improving-performance.md).
* For the Data Center Edition on Kubernetes: set up autoscaling. See [Setting up autoscaling](/sonarqube-server/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-autoscaling.md) for more details.
* If performance issues occur after a PostgreSQL database upgrade, try reindexing the following database tables: issues, rules, and components.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Server logs](/sonarqube-server/2026.2/server-update-and-maintenance/troubleshooting/server-logs.md)
* [Database-related issues](/sonarqube-server/2026.2/server-update-and-maintenance/troubleshooting/database-related-issues.md)
* [Elasticsearch-related issues](/sonarqube-server/2026.2/server-update-and-maintenance/troubleshooting/elasticsearch.md)
* [Other issues](/sonarqube-server/2026.2/server-update-and-maintenance/troubleshooting/other-issues.md)
* [Improving performance](/sonarqube-server/2026.2/server-update-and-maintenance/maintenance/improving-performance.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2026.2/server-update-and-maintenance/troubleshooting/performance-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.