Concurrent URL checks spend most time waiting for network responses.
Understanding the Concept
Concurrent URL checks spend most time waiting for network responses. Use bounded worker counts, timeouts and allowed destinations rather than launching unlimited requests.
The example is deliberately offline; real HTTP code must handle TLS, redirects, SSRF and network failures.
How to reason about concurrent execution
Workers may start and finish in a different order on every run. Focus on ownership of data, how work and errors move between workers, and what happens when one worker stops early. Locks protect invariants, queues exchange messages, and explicit shutdown logic prevents blocked or orphaned workers.
Concurrency adds overhead and failure modes. Begin with a working sequential solution, choose bounded worker counts and explicit timeouts, then measure whether overlap or parallel execution improves the target workload.
Worked Example
Read the code from the first line to the last. Identify which values are inputs, which operation is being demonstrated and what should happen before running it.
from concurrent.futures import ThreadPoolExecutor
def fake_status(address):
# Offline demonstration; replace with an approved HTTP client.
return address, "not checked: offline example"
with ThreadPoolExecutor(max_workers=2) as pool:
print(list(pool.map(fake_status, ["https://example.org", "https://example.com"])))Walkthrough: What Each Part Does
- The imports make concurrent.futures available. These are standard-library building blocks unless the example explicitly names an external tool.
- The definition fake_status creates reusable behavior. Its body runs when called, awaited or instantiated; defining it alone does not run the body of an ordinary function.
- The with or async with scope controls lifetime. Setup takes place on entry, and cleanup runs on exit even when an exception interrupts the body.
- The last lines coordinate completion and inspect results. Actual worker scheduling may differ between executions.
This demonstration focuses on one practical behavior. Before changing several lines, vary one input or one configuration choice and check whether the result changes for the reason you expected.
Example Output
[('https://example.org', 'not checked: offline example'), ('https://example.com', 'not checked: offline example')]The output above was captured by running the example in the available Python environment. The order of concurrent events, durations and platform-dependent values can legitimately differ on your computer.
Important Behavior and Edge Cases
Issuing unrestricted requests to user-supplied internal addresses or omitting request timeouts.
The example is deliberately offline; real HTTP code must handle TLS, redirects, SSRF and network failures.
Practice Exercise
Write a network-enabled version for two authorized test endpoints with retry limits and safe URL validation.
Write down the result you expect before running your changed code. Check at least one normal case and one boundary or failure case. If your example starts workers or opens resources, verify how they are cleaned up.
Further reading: official documentation and API reference.
Common Beginner Mistakes
- Issuing unrestricted requests to user-supplied internal addresses or omitting request timeouts.
- Forgetting to handle worker errors and shutdown, even when the normal completion path appears correct.
Key Takeaways
- Concurrent URL checks spend most time waiting for network responses.
- The example is deliberately offline; real HTTP code must handle TLS, redirects, SSRF and network failures.
- Practice: Write a network-enabled version for two authorized test endpoints with retry limits and safe URL validation.