> 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/parallels-desktop-developers-guide/software-development-specific-functions-of-parallels-desktop/simulating-adverse-network-connectivity-conditions.md).

# Simulating Adverse Network Connectivity Conditions

In software development, it may be beneficial to simulate various network conditions (low speeds, high packet loss, etc.) to see how your app behaves and eliminate potential sources of complaints. Parallels Desktop allows you to do just that by applying machine-specific connection profiles that mimic popular scenarios. To choose from a variety of preset options, do the following:

1. In Parallels Desktop Control Center, right-click on the required virtual machine and choose **Configure**.
2. Switch to the **Hardware** tab and choose **Network** from the list on the left.
3. Use the Profile drop-down menu to select one of the preset scenarios.
4. Alternatively, click on **Configure** to manually adjust speeds, pings, and packet loss percentages as required.

<figure><img src="https://642364226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNS18wNNEob8E86PpkwMT%2Fuploads%2Fc6A1VYVAJ1vS3EW87obR%2FScreenshot%202024-01-25%20at%2012.59.45.png?alt=media&amp;token=b8557bd4-7616-4dbe-9871-252f1ac9be48" alt="" width="496"><figcaption></figcaption></figure>


---

# 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/parallels-desktop-developers-guide/software-development-specific-functions-of-parallels-desktop/simulating-adverse-network-connectivity-conditions.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.