.png.80db469bbb5f2538f9ecd701958d53cb.png)
Multithreading is important for the program. Each flow is actually an individual, which will work for you. Multithreading is divided into 2 parts, browser and post / get requests, used to determine cms. You can configure the flows for each part. The browser is resource- intensive and it is impossible to specify hundreds of threads in it, but in post/get the requests are simple and execution can go to 300 or more threads.
The standard version has limitations:
- 3 threads for one browser.
- 15 threads for post/get requests.
You can’t set more value. Premium versions don’t have limitations. The only limitation is your computer resources.
We recommend to make several test runs, run the task manager and look at the system workload, focusing on this, to choose the optimal number of threads for the browser. For post/get requests, the program is able to focus on the available resources number and will not run more ones than possible.
To get started, if you do not have a dual-core 2.1 GHz processor (if you have a weak processor, start working with 3 threads), you can put 10 threads for the browser and 150 for post/get and based on these values, an important condition is not to allow a constant 100% load on the processor. The computers characteristics are very different and we can’t provide specific information about the optimal values for each system. Additionally, each resource downloaded in the browser, can have different effects on performance.
- It is impossible to change the number of threads during cms analysis during the runtime. The value can only be changed before the start.
- It is impossible to change the threads number in the browser during the runtime, but it can be changed by pausing the program, waiting for all threads are finished, changing the number, saving and running the execution again.