Optimizing Performance: Timeout and Concurrency Controls
AxelBase handles thousands of links with ease, but the right configuration can turn a 5-minute scan into a 30-second breeze.
Understanding the Core Controls
Two key settings determine how the tool interacts with the web. Finding the right balance is key to accurate results:
| Setting | What it does | Effect of Increasing |
|---|---|---|
| Timeout | Wait time for server response | Fewer "false" timeouts, but slower overall scan. |
| Concurrency | Number of parallel requests | Much faster scans, but risks rate-limiting/CPU lag. |
Concurrency: The Power of Parallelism
Concurrency controls how many links are tested at the exact same time. Modern browsers support several simultaneous connections per domain. By raising this setting, you can validate massive documentation sets in a fraction of the time.
The "Sweet Spot"
Extremely high concurrency (50+) can cause some servers to view your browser as a bot and block your IP. If you see a sudden spike in 429 (Too Many Requests) errors, lower your concurrency immediately.
Practical Tuning Strategies
Depending on your hardware and network, try these common configurations:
Fast Office Fiber
- Concurrency: 25-35
- Timeout: 5,000ms
- Result: Lightning speed for huge files.
Public Wi-Fi / Mobile
- Concurrency: 5-10
- Timeout: 15,000ms
- Result: Higher reliability on unstable links.
The following article explains how to exclude unwanted domains and patterns so checks stay focused and efficient.