> 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/2025.3/server-update-and-maintenance/troubleshooting/performance-issues.md).

# Performance issues

Steps to consider when addressing performance issues in SonarQube Server 2025.3.

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

* Review the [Server host requirements](/sonarqube-server/2025.3/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/2025.3/server-installation/from-zip-file/basic-installation.md#configure-es-storage-path) for more information.
* Set the [Housekeeping](/sonarqube-server/2025.3/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 the Analysis scope [Introduction](/sonarqube-server/2025.3/project-administration/setting-analysis-scope/introduction.md) page 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/2025.3/server-update-and-maintenance/maintenance/improving-performance.md).
* For the Data Center Edition on Kubernetes: set up autoscaling. See [Setting up autoscaling](/sonarqube-server/2025.3/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/2025.3/server-update-and-maintenance/troubleshooting/server-logs.md)
* [Database-related issues](/sonarqube-server/2025.3/server-update-and-maintenance/troubleshooting/database-related-issues.md)
* [Elasticsearch-related issues](/sonarqube-server/2025.3/server-update-and-maintenance/troubleshooting/elasticsearch.md)
* [Other issues](/sonarqube-server/2025.3/server-update-and-maintenance/troubleshooting/other-issues.md)
* [Improving performance](/sonarqube-server/2025.3/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.