> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-linux-client-guide/v20/using-parallels-client-for-linux/configuring-a-ras-connection/experience.md).
# Experience
The **Experience** tab page allows you to tweak the connection speed to optimize the performance of the connection with the remote server.
In the drop-down list, select your connection speed:
* If not sure, select the **Detect connection quality automatically** option. Please note that if you select this option, all other options will be disabled and will be configured automatically based on the actual connection speed when Parallels Client is connected to Parallels RAS.
* If you select a specific speed (e.g. LAN 10 Mbps or higher), select the desired user experience options. If you are connecting to a remote computer on a local network that runs at 100 Mbps or higher, it is usually safe to have all of the experience options turned on. Otherwise, select only the options that you require.
---
# 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.parallels.com/landing/ras-linux-client-guide/v20/using-parallels-client-for-linux/configuring-a-ras-connection/experience.md?ask=&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.
