> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/fr/knowledge-base/troubleshooting-articles/high-cpu-usage.md).

# Utilisation élevée du processeur

Corrigez l'utilisation élevée du processeur dans Remote Desktop Manager 13 et versions ultérieures dans les environnements RDS en désactivant la fonctionnalité de vérification de l'état des entrées.

Avec un espace de travail SQL, si vous constatez une utilisation élevée du processeur sur vos systèmes, particulièrement dans un environnement Terminal Services / services Bureau à distance (RDS), cela peut être causé par la fonctionnalité de vérification de l'état des entrées.

### Solution

Désactivez l'option ***Allow entry states (locked, running, checked out)*** dans ***Administration – System settings – Vault*** pour améliorer la performance sur vos serveurs et vos postes de travail.


---

# 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.devolutions.net/rdm/fr/knowledge-base/troubleshooting-articles/high-cpu-usage.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.