Last updated: July 20, 2021
Read time: 5 Minutes
There are circumstances in which Burp Suite can run slowly. In this section, we'll describe some quick steps you can take to troubleshoot performance issues in Burp Suite and increase the efficiency of your testing.
All editions of Burp Suite require 64-bit hardware. For the best experience with Burp Suite Professional, we recommend using a machine with at least 8 GB of memory and 2 CPU cores. If you are performing large amounts of work, or testing large or complex applications, you may need a more powerful machine than this.
Burp Suite places additional load on your machine's CPU and memory, and on the network over which it runs.
Manage Burp's CPU use by disabling certain features and configuring scans in the following ways:
Burp Scanner has many configurable options for optimizing performance during both the crawl and audit phases. Configure scans to improve performance as follows:
To optimize performance during crawling:
To optimize performance during auditing:
Ensure that you are only scanning the areas of the target site that you are interested in. Narrowing your scope will improve performance. Fine-tune the scope of a scan from the "Detailed scope configuration" area of the scan launcher.
If your target only supports one of HTTP and HTTPS, ensure that Burp Scanner only sends requests using the supported protocol. In "Scan details", in the "URLs to scan" section, include the desired protocol in each URL that you want to scan. Then select "Scan using my specified protocols" in the same area.
Optimize your memory usage in the following ways:
Burp Suite extensions are useful, but can increase the load on your system. PortSwigger does not test extensions for resource optimization and some extensions will impact Burp Suite's performance. It is best to be cautious about the extensions you use and remove any that you do not need. If Burp Suite appears to be using an excessive amount of memory, try disabling your extensions one by one to discover if any of them are causing problems.
Burp Suite is constrained by the amount of memory your machine allocates to Java. If you launch Burp from the command line, you can use command line arguments to allocate more memory. The procedure is detailed here.
Temporary projects have more demands on memory than disk-based projects, as all the project data needs to be stored in memory rather than on a disk. If your memory use is maximized, switching to a disk-based project will move some of the load from memory to a hard disk. However, note that RAM is faster than hard drives, and it's possible that doing this will introduce delays, especially if your disks are slow (e.g. hard disk drives rather than solid state drives). You may need to experiment to see whether disk-based or temporary projects are faster for you. You can convert a temporary project to a disk-based project by going to the Project menu and selecting "Save copy".
Manage network issues in the following ways:
To reduce the load on your network, reduce the number of scans running together.
Burp Suite can overload target applications by sending requests faster than a target can handle or will allow during active scans. Stop requests hanging or timing out by reducing the number of requests that Burp Suite makes at once: