> 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-windows-client-guide/using-parallels-client-for-windows/using-a-ras-connection/assessing-network-performance.md).

# Assessing Network Performance

When users experience poor performance while working with remote applications or desktops in Parallels Client, the issue may not be related to back-end Parallels RAS components, but simply due to poor network conditions. Parallels Client provides you with the ability to assess network performance while an active session is running.

To asses network performance, click main menu > **Session Information**. The **Sessions** dialog opens where you can view active session information.

<figure><img src="https://download.parallels.com/ras/v19/docs/en_US/Parallels-Client-for-Windows-19-User-Guide/win-session-info.png" alt=""><figcaption></figcaption></figure>

The columns in the **Sessions** table are:

* **Session.** Session name.
* **Server.** Remote server name or IP address.
* **Connection Quality**. Can be one of the following: Poor, Fair, Good, Excellent.
* **Latency**. Connection round-trip delay time, in milliseconds.
* **Bandwidth**. Connection bandwidth.
* **Username**. Username of the session owner.
* **Domain**. Domain name.
* **Type**. Connection type (RAS or RDP).

The **Connection Quality**, **Latency**, and **Bandwidth** column values should give you enough information to identify poor network conditions. If network performance is not as expected, you can address the issue from this perspective. You can also view the connection quality information on the **Session Information** dialog (**Connection Quality** section). To open the dialog, select a session and click the **Show Information** button.

The buttons in the **Sessions** dialog allow you to perform the following actions:

* **Refresh.** Refresh the **Sessions** list.
* **Show Information**. Display additional session information, including credentials and the Gateway used, connection mode, encryption, and others.
* **Disconnect**. Disconnect from Parallels RAS. The resource (or resources) will be closed on your local desktop, but will continue to run on the remote server. If you open the resource after that, your work will be where you left it. If you had more than one instance of a resource opened before you disconnected from Parallels RAS, all of them will open on your desktop.
* **Logoff**. End the session. This will close all running resources on the remote server. You should save all your data before ending a session.
* **Close**. Close the **Sessions** dialog.


---

# 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-windows-client-guide/using-parallels-client-for-windows/using-a-ras-connection/assessing-network-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.
