# Digma Overload Warning

<figure><img src="/files/ioOIGut5dbtZLziRrSD0" alt=""><figcaption></figcaption></figure>

### Overload when using Digma locally

Since Digma is running locally on your development machine, it is set up to avoid consuming too much CPU resources. Therefore, instead of scaling up to handle traces concurrently, when Digma reaches a certain throughput limit, it will begin throttling incoming observability data. In essence, this means that some of the incoming traces will be dropped and Digma will continue to process traces at the same speed as before.

If you've received the `Digma Overloaded` warning and you would like to scale up Digma to process the additional data - you can [install a Centralized Digma](/digma-developer-guide/installation/central-on-prem-install.md) on a local Kubernetes cluster.

### Overload when using Digma centrally

When deploying Digma centrally, the Analytics Engine will scale based on the deployment configuration. Digma will monitor the size of its queues to detect if it is still unable to catch up with incoming data. In such a scenario, Digma must begin throttling or else risk running out of memory or accumulating too much lag. In such a scenario, you will receive a message that throttling is in place. One way to avoid this state is to deploy Digma using a larger deployment size.  See the [central install documentation](/digma-developer-guide/installation/central-on-prem-install.md) for more details.


---

# Agent Instructions: 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:

```
GET https://docs.digma.ai/digma-developer-guide/troubleshooting/digma-overload-warning.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.