Configuring Timeout and Concurrency Settings

Performance and reliability during link validation depend heavily on network conditions and document size. The Markdown Link Checker provides two key configuration options—timeout and concurrency—to help you balance speed, accuracy, and browser resource usage.

These settings appear in the configuration panel and update dynamically without page reloads.

Understanding Timeout

The timeout value specifies how long each link check waits for a server response before giving up. Measured in milliseconds, the default sits at a reasonable middle ground, but you may need adjustment based on your environment.

Slow or distant servers benefit from higher timeouts to avoid false positives. Fast local networks or strict workflows prefer lower values to fail unresponsive links quickly. Extremely high settings risk long hangs if many links are dead.

Concurrency Limit

Concurrency controls how many link checks run simultaneously. The default of five parallel requests works well for most users, delivering quick results without overwhelming browser or network resources.

Increasing concurrency speeds up validation for documents with hundreds of links, especially on powerful machines with good bandwidth. However, too many simultaneous requests can trigger rate limiting from servers, exhaust memory, or slow down other browser tabs.

Lower values prove useful on slower connections, mobile devices, or when checking many links to the same domain that might impose rate limits.

Finding the Right Balance

Start with defaults for typical use. For large documentation sets on fast connections, try raising concurrency to ten or fifteen. When dealing with flaky networks, extend timeout to ten seconds and reduce concurrency to three.

The real-time progress indicator helps you observe how changes affect overall validation time. Experiment freely—settings persist only for the current session and never affect privacy.

Practical Scenarios

Checking internal documentation behind corporate firewalls often requires longer timeouts. Validating public open-source projects with many external references benefits from higher concurrency. Pre-publish checks on laptops favor conservative settings to avoid browser strain.

These controls put you in charge of the validation experience, adapting the tool to your specific workflow and constraints.

Tuning timeout and concurrency transforms good results into optimal ones tailored to your needs.

Fine-tune settings for faster, more reliable link checks every time.