> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/performance.md).

# Memory, storage and performance

Memory, disk, swap and connection pools — the host running out of something, or a service not allowed enough of it.

Work out which resource is short before changing a limit: raising one service's ceiling on a host that is already short of memory moves the failure rather than fixing it.

## Find out what is short

* [Check memory utilization](/troubleshooting/performance/memoryutili.md) — what each Java service is allowed, and what it is using
* [Redis memory utilization](/troubleshooting/performance/redismemory.md) — what the cache holds, whether it has a cap, and what happens at it
* [Running out of disk space](/troubleshooting/performance/lackof_disk_space.md)

## Then change it

* [Increasing memory for OpenIAM services](/troubleshooting/performance/increasing-ram.md)
* [Increasing the JDBC connection pool size](/troubleshooting/performance/jdbc-connection-pool.md)
* [Disable swap](/troubleshooting/performance/disableswap.md) — a requirement rather than a tuning option
* [The My Applications page is slow to reflect a change](/troubleshooting/performance/my-application-page-selfservice.md) — a cache timer, not a resource problem

{% hint style="info" %}
**On Kubernetes, memory and heap are deployment settings** rather than troubleshooting steps — see [Tuning](/installation/tuning.md).
{% endhint %}


---

# 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.openiam.com/troubleshooting/performance.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.