When performing scans, you might want to limit the rate at which requests are made. Burp 1.x had settings for request throttling within the Spider and Scanner tools. These settings applied to all requests made by the applicable tool. Burp 2.x introduces the concept of resource pools, which let you apply request throttling at the task level.

Burp 1.x

In Burp 1.x, you could throttle the Spider and Scanner tools using the relevant engine settings:


Burp 2.x

You can now use Burp's resource pool options to configure throttling settings that are applied to one or more tasks.

Each resource pool can be configured with the number of requests that can be made concurrently, or the rate at which requests can be made, or both.


You can add more than one task to a resource pool. So, for example, you can create a fast resource pool for tasks that don't need to be throttled, and a slow resource pool for tasks where the rate of requests needs to be controlled.