> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.beaglesecurity.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Test speed settings: Slow, medium & fast

Beagle Security allows you to control the speed at which penetration tests are performed. You can configure a default test speed for all applications or set a different speed for a specific application. Test speed affects both how quickly requests are sent during testing and the overall time required to complete a test. Choosing the appropriate speed helps ensure effective testing while minimizing any impact on your application.

# Method 1: Set a default test speed
Use this method if you want all new tests to use the same speed by default.

* Click **Settings**.

* Select **Test Settings**.

* Scroll down to **Test speed**.

* Choose your preferred speed.

* Save your changes.

### Understanding the test speeds
###### Slow
Sends requests at a minimal rate and is suitable for websites with limited server capacity or environments where traffic should be kept to a minimum.

It is recommended for production environments with low traffic tolerance. Slow speed can also be beneficial for applications that rely on asynchronous logging, rate limiting, edge functions, or other similar workflows, as it gives requests more time to complete before additional requests are sent.

Choosing this option will result in longer test durations.

###### Medium
Uses a balanced request rate and is suitable for most applications.

This option provides a good balance between testing speed, application stability, and overall test performance. For most applications, Medium is the recommended starting point.

###### Fast
Sends requests at a higher rate and completes tests more quickly.

This option is recommended only for applications hosted in scalable environments that can comfortably handle increased traffic without disruption.

Applications with strict rate limiting, asynchronous processing, or limited server capacity may benefit from using a slower test speed instead.

![](https://storage.crisp.chat/users/helpdesk/website/-/f/6/7/c/f67cd8fc6fde8000/test-speed-ss-2_mb9jik.png)
# Method 2: Setting the test speed for a specific application
Use this method when you want a particular application to use a different speed than the default setting.

* Go to **Applications**.

* Select the application you want to configure.

* Click on the **Configuration** tab.

* Click **Advanced**.

* Scroll down to **Test speed** and click on it.

A configuration pop up will open, allowing you to select the desired speed.

![](https://storage.crisp.chat/users/helpdesk/website/-/f/6/7/c/f67cd8fc6fde8000/test-speed-ss_mo2ayo.png)
### Estimated durations
The selected speed also affects the expected test completion time.

* **Slow**: Up to 5 days

* **Medium**: Up to 3 days

* **Fast**: Up to 2 days

These durations may vary depending on the size and complexity of the application being tested.

# Choosing the right speed
For most applications, **Medium** provides the best balance between testing efficiency and application stability.

Consider using **Slow** when testing production environments with limited traffic tolerance or applications that depend on asynchronous processing, logging, rate limiting, or edge-function workflows.

Use **Fast** only when the application is hosted in an environment that can safely handle increased testing traffic.