Simultaneous visits (threads)
Threads control how many browser processes run at once. The slider spans 1 to 50, but 10 is the safe ceiling and higher values must be unlocked deliberately. Threads are global, not per project, so running two projects at once splits them between the two.
Every simultaneous visit is a separate browser process with its own memory, its own device profile and its own proxy. The thread count is how many of those run at the same time.
It is a global setting
This surprises people. The slider is labelled Global for all projects, and it means it. If you set 10 threads and start two projects, they get roughly 5 each — not 10 each.
Starting a third project splits them three ways, and stopping one gives its share back to the others. Plan your total, not your per-project number.
The safe ceiling
The slider runs from 1 to 50, but the track is colour-coded and the handle is locked at 10 until you unlock the high-resource zone. That lock is a deliberate speed bump, not a formality.
| Your RAM | Comfortable threads |
|---|---|
| 4 GB | 2 to 4 |
| 8 GB | 5 to 8 |
| 16 GB | 9 to 16 |
| 32 GB | 17 to 32 |
Your network matters too. Each thread downloads a full page. On a slow connection, ten threads will time out long before your CPU is the problem.
What too many threads looks like
Overloading does not produce a clear error. It produces page load timeouts logged as failed visits, which is easy to misdiagnose as a proxy or site problem.
If your success rate drops as you raise threads, and the log is full of timeouts rather than proxy errors, you have gone too far. Lower it until the rate recovers.
Turning off Load Images reduces bandwidth and memory per visit noticeably, and has no effect on analytics. It is the cheapest way to support more threads on modest hardware.
Threads and your visit rate
Threads are one of the two things that determine throughput. The other is how long each visit lasts:
visits per hour = threads × 3600 ÷ average visit length (seconds)Doubling threads roughly doubles your rate, at roughly double the memory cost. Doubling stay time roughly halves it, at no extra cost. If you want fewer visits, lengthen stays rather than cutting threads — longer visits also look more realistic.
Changing threads while running
The thread slider can be adjusted while projects are running, and the change is applied as visits finish and restart. You do not need to stop anything.
The engine setting is different — that cannot be changed mid-run. Stop the project first.
Choosing a number
- Testing a setup: 2 threads. The log stays readable and problems are obvious.
- Normal running: 4 to 8 on a typical machine.
- Load testing: unlock the higher range, but raise gradually and watch the success rate at each step.
Last updated: