> 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/knowledge-base/troubleshooting-articles/workspace-performance.md).

# Workspace performance

Speed up slow Remote Desktop Manager workspace loads and refreshes caused by custom entry images or RTF descriptions with embedded images.

A large workspace configuration slows down every operation that reads entries from the workspace:

* The initial load when Remote Desktop Manager starts.
* Editing an entry, since Remote Desktop Manager reloads the entry first to make sure you work on its current version.
* Opening a session, since Remote Desktop Manager writes the activity to the logs.
* Refreshing the workspace. Depending on your cache settings, a refresh typically only retrieves the changes made since the last refresh.

The causes below increase the size of the configuration and are the most common reasons for slow workspace operations.

{% hint style="info" %}
With the default configuration, SQL Server databases also degrade over time. See [SQL Server performance troubleshooting](/rdm/knowledge-base/troubleshooting-articles/sql-server-performance-troubleshooting.md).
{% endhint %}

### Slow workspace due to custom entry images

#### Cause

Custom images are stored in the workspace with each entry that uses them. When many entries use custom images, the size of the configuration grows and every load or refresh takes longer.

#### Solution

Use the built-in images instead of custom images on as many entries as possible.

### Slow workspace due to images in entry descriptions

#### Cause

RTF descriptions do not affect performance on their own. Images embedded in RTF descriptions, however, are stored in the workspace like custom images and increase the size of the configuration.

#### Solution

Remove embedded images from the descriptions, or reduce their size.


---

# 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/knowledge-base/troubleshooting-articles/workspace-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.