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

# Performance issues

Steps to try if you have performance issues with SonarQube Server 10.8.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.8 documentation. For a list of all 10.8 pages, see the [SonarQube Server 10.8 page index](https://312504542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiJj3TXBdWssTGGg8qK5I%2Fuploads%2FmeJ1nVNGPezOurNrTy4A%2Fsonarqube-server-10.8-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.8 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

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

* Review the [SonarQube Server host](/sonarqube-server/10.8/setup-and-upgrade/installation-requirements/server-host.md) for SonarQube Server linked to **Elasticsearch** usage.
* Move the Elasticsearch storage to a storage with high IOPS and low latency: see **Configure the Elasticsearch storage path** in [Installing from the ZIP file](/sonarqube-server/10.8/setup-and-upgrade/install-the-server/installing-sonarqube-from-zip-file.md).
* Set the [Housekeeping](/sonarqube-server/10.8/instance-administration/system-functions/housekeeping.md) with a reduced retention time, to limit the database size.
* Configure the [Analysis scope](/sonarqube-server/10.8/project-administration/analysis-scope.md) to reduce the number of files analyzed, leading to shorter analysis and smaller database footprint.
* 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/10.8/server-upgrade-and-maintenance/maintenance/improving-performance.md).
* For the Data Center Edition on Kubernetes: set up [Setting up autoscaling](/sonarqube-server/10.8/setup-and-upgrade/deploy-on-kubernetes/setting-up-autoscaling.md).
* 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>

* [Checking the server logs](/sonarqube-server/10.8/server-upgrade-and-maintenance/troubleshooting/checking-server-logs.md)
* [Database-related issues](/sonarqube-server/10.8/server-upgrade-and-maintenance/troubleshooting/database-related-issues.md)
* [Elasticsearch-related issues](/sonarqube-server/10.8/server-upgrade-and-maintenance/troubleshooting/elasticsearch.md)
* [Other issues](/sonarqube-server/10.8/server-upgrade-and-maintenance/troubleshooting/other-issues.md)
* [Improving performance](/sonarqube-server/10.8/server-upgrade-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/10.8/server-upgrade-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.