🌐
GitHub
github.com › pyiron › executorlib
GitHub - pyiron/executorlib: Up-scale python functions for high-performance computing (HPC) · GitHub
Only the part of the Python functions which benefit from parallel execution are implemented as MPI parallel Python funtions, while the rest of the program remains serial. The same function can be submitted to the SLURM job scheduler by replacing the SingleNodeExecutor with the SlurmClusterExecutor. The rest of the example remains the same, which highlights how executorlib accelerates the rapid prototyping and up-scaling of HPC Python programs.
Starred by 72 users
Forked by 6 users
Languages   Python 63.4% | Jupyter Notebook 36.6%
🌐
GitHub
github.com › Joldnine › joldnine.github.io › issues › 10
Python: Submit multi parameters function to Executor · Issue #10 · Joldnine/joldnine.github.io
December 28, 2017 - from concurrent.futures import ThreadPoolExecutor def say_something (var1, var2): print('{}: {}'.format(var1, var2)) arr1 = ['name', 'Joldnine'] arr2 = ['email', 'heyhey@hey.com'] pool = ThreadPoolExecutor(2) pool.submit(lambda p: say_something(*p), arr1) pool.submit(lambda p: say_something(*p), arr2)
Author   Joldnine
🌐
GitHub
github.com › python › typeshed › issues › 7750
concurrent.futures: Bad signature for Executor.submit() under Python <= 3.8 · Issue #7750 · python/typeshed
April 30, 2022 - python3.8 -m venv /tmp/py38 source /tmp/py38/bin/activate pip -q install mypy stubtest concurrent.futures · diff --git a/stdlib/concurrent/futures/_base.pyi b/stdlib/concurrent/futures/_base.pyi index 5b756d87..fc6a342c 100644 --- a/stdlib/concurrent/futures/_base.pyi +++ b/stdlib/concurrent/futures/_base.pyi @@ -60,7 +60,7 @@ class Future(Generic[_T]): def __class_getitem__(cls, item: Any) -> GenericAlias: ... class Executor: - if sys.version_info >= (3, 9): + if sys.version_info >= (3, 8): def submit(self, __fn: Callable[_P, _T], *args: _P.args, **kwargs: _P.kwargs) -> Future[_T]: ...
Author   dalcinl
🌐
GitHub
github.com › rohanpm › more-executors
GitHub - rohanpm/more-executors: Library of composable Python executors
import requests from concurrent.futures import as_completed from more_executors import Executors def get_json(response): response.raise_for_status() return (response.url, response.json()) def fetch_urls(urls): # Configure an executor: # - run up to 4 requests concurrently, in separate threads # - run get_json on each response # - retry up to several minutes on any errors executor = Executors.\ thread_pool(max_workers=4).\ with_map(get_json).\ with_retry() # Submit requests for each given URL futures = [executor.submit(requests.get, url) for url in urls] # Futures API works as normal; we can block on the completed # futures and map/retry happens implicitly for future in as_completed(futures): (url, data) = future.result() do_something(url, data) virtualenv and pip may be used to locally install this project from source: virtualenv ~/dev/python .
Starred by 27 users
Forked by 6 users
Languages   Python 99.2% | Python 99.2%
🌐
GitHub
github.com › dchevell › flask-executor
GitHub - dchevell/flask-executor: Adds concurrent.futures support to Flask · GitHub
Code that must be run in these contexts or that depends on information or configuration stored in flask.current_app, flask.request or flask.g can be submitted to the executor without modification. Note: due to limitations in Python's default object serialisation and a lack of shared memory ...
Starred by 180 users
Forked by 26 users
Languages   Python
🌐
GitHub
github.com › python › cpython › blob › main › Lib › concurrent › futures › thread.py
cpython/Lib/concurrent/futures/thread.py at main · python/cpython
submit.__doc__ = _base.Executor.submit.__doc__ · def _adjust_thread_count(self): # if idle threads are available, don't spin new threads · if self._idle_semaphore.acquire(timeout=0): return · · # When the executor gets lost, the weakref callback will wake up ·
Author   python
🌐
GitHub
github.com › syogaraj › scheduled_thread_pool_executor
GitHub - syogaraj/scheduled_thread_pool_executor: Scheduled Thread Pool Executor implementation in python
Scheduled Thread Pool Executor implementation in python · Makes use of delayed queue implementation to submit tasks to the thread pool.
Author   syogaraj
🌐
GitHub
github.com › xolox › python-executor
GitHub - xolox/python-executor: Programmer friendly subprocess wrapper · GitHub
The command line interface is described below and there are also some examples of simple use cases of the Python API. ... Usage: executor [OPTIONS] COMMAND ...
Starred by 106 users
Forked by 28 users
Languages   Python 99.2% | Makefile 0.8%
🌐
GitHub
github.com › kaleksandrov › python-thread-pool-executor
GitHub - kaleksandrov/python-thread-pool-executor: A thread pool executor implementation written in python · GitHub
executor.start() # Submit any number of tasks. When a task is submited if # there is a waiting thread, it starts executing it, # otherwise - the tasks remains in a queue. Once a thread # becomes available it checks in the queue for pending tasks. ...
Author   kaleksandrov
Find elsewhere
🌐
Alexwlchan
alexwlchan.net › 2019 › adventures-with-concurrent-futures
Adventures in Python with concurrent.futures – alexwlchan
We don't want to schedule them all # at once, to avoid consuming excessive amounts of memory. futures = { executor.submit(perform, task): task for task in itertools.islice(tasks_to_do, HOW_MANY_TASKS_AT_ONCE) } while futures: # Wait for the next future to complete.
🌐
GitHub
github.com › PrefectHQ › prefect › issues › 2847
Executor submit and wait interfaces are asymmetrical · Issue #2847 · PrefectHQ/prefect
import concurrent import contextlib import prefect class MyExecutor(prefect.engine.executors.base.Executor): def __init__(self): super().__init__() @contextlib.contextmanager def start(self): self.exec = concurrent.futures.ThreadPoolExecutor() yield self.exec def submit(self, fn, *args, **kwargs): return self.exec.submit(fn, *args, **kwargs) def wait(self, futures): results = [] for f in futures: results.append(f.result()) # block until future returns return results
Author   ghost
🌐
GitHub
github.com › wdk-docs › python-documentation › blob › master › docs › library › concurrent.futures.rst
python-documentation/docs/library/concurrent.futures.rst at master · wdk-docs/python-documentation
Regardless of the value of *wait*, the entire Python program will not exit until all pending futures are done executing. You can avoid having to call this method explicitly if you use the :keyword:`with` statement, which will shutdown the :class:`Executor` (waiting as if :meth:`Executor.shutdown` were called with *wait* set to ``True``):: import shutil with ThreadPoolExecutor(max_workers=4) as e: e.submit(shutil.copy, 'src1.txt', 'dest1.txt') e.submit(shutil.copy, 'src2.txt', 'dest2.txt') e.submit(shutil.copy, 'src3.txt', 'dest3.txt') e.submit(shutil.copy, 'src3.txt', 'dest4.txt')
Author   wdk-docs
Top answer
1 of 3
2

You have:

with concurrent.futures.ThreadPoolExecutor(16) as executor:
    executor.submit(f1)

The main thread submits a task specifying worker function f1. Then the main thread exits the block and an implicit call to executor.shutdown() is made. Any tasks already submitted and have started to execute will complete but onceshutdown is called submitted tasks that have not yet started execution will be thrown away. In your code the call to shutdown occurs before worker function f1 has had a chance to submit the new task with f2 as the worker function and get its execution started. This can be demonstrated as follows:

with concurrent.futures.ThreadPoolExecutor(16) as executor:
    executor.submit(f1)
    import time
    time.sleep(.1)

We have delayed the call to shutdown by .1 seconds giving f1 a chance to get f2 started. But even this has a race condition: Is .1 seconds always enough time to allow f1 to submit the second task and for that task to start? We cannot depend on this method.

TL;DR

You can skip to the final section Solution if you wish and not read the following solutions for simpler cases.

Attempts

To remove that race condition we can use a multithreading.Event that gets set only after all tasks that we need to submit have started executing:

import concurrent.futures
from threading import Event

all_tasks_submitted = Event()

def f2():
    all_tasks_submitted.set()
    print("hello, f2")
    return 3


def f1():
    print("hello, f1")
    print(executor.submit(f2).result())


with concurrent.futures.ThreadPoolExecutor(16) as executor:
    executor.submit(f1)
    all_tasks_submitted.wait()

Prints:

hello, f1
hello, f2
3

So now let's look at your actual case. First, there is a slight bug: f2 takes only two arguments but f1 is trying to invoke it with 3 arguments.

This is far more complicated case in that we are ultimately trying to start 10 * 10 * 10 = 1000 f3 tasks. So we now need a counter to keep track of how many f3 have been started:

import concurrent.futures
from threading import Event, Lock

all_tasks_started = Event()
lock = Lock()


NUM_F3_TASKS = 1_000
total_f3_tasks_started = 0

def f3(arg1, arg2):
    global total_f3_tasks_started

    with lock:
        total_f3_tasks_started += 1
        n = total_f3_tasks_started

    if n == NUM_F3_TASKS:
        all_tasks_started.set()

    print(f"hello, f3, {arg1}, {arg2}, f3 tasks started = {n}")


def f2(arg1, arg2):
    print(f"hello, f2 {arg1}")
    for i in range(10):
        executor.submit(f3, arg2, i)


def f1(arg1, arg2, arg3):
    print(f"hello, f1 {arg1}")
    for i in range(10):
        executor.submit(f2, arg2, arg3)


with concurrent.futures.ThreadPoolExecutor(16) as executor:
    for i in range(10):
        executor.submit(f1, i, 1, 2)
    all_tasks_started.wait()

Prints:

hello, f1 0
hello, f1 1
hello, f1 2
hello, f1 3
hello, f1 4
hello, f1 5
hello, f1 6
hello, f1 7
hello, f1 8
hello, f1 9
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1

...

hello, f3, 2, 2, f3 tasks started = 993
hello, f3, 2, 4, f3 tasks started = 995
hello, f3, 2, 6, f3 tasks started = 997
hello, f3, 2, 8, f3 tasks started = 999
hello, f3, 2, 3, f3 tasks started = 994
hello, f3, 2, 7, f3 tasks started = 998
hello, f3, 2, 5, f3 tasks started = 996
hello, f3, 2, 9, f3 tasks started = 1000

But this means that you need to know in advance exactly how many f3 tasks need to be created. You might be tempted to solve the problem by having f1 not return until all tasks it has submitted complete and having f2 not return until all tasks it has submitted complete. You would thus be having a 10 f1 tasks, 100 f2 tasks and 1000 f3 tasks running concurrently for which you would need a thread pool of size 1110.

Solution

We use an explicit task queue and a task executor as follows:

import concurrent.futures
from queue import Queue
from threading import Lock

task_queue = Queue()
lock = Lock()

task_number = 0

def f3(arg1, arg2):
    global task_number

    with lock:
        task_number += 1
        n = task_number

    print(f"hello, f3, {arg1}, {arg2}, task_number = {n}")


def f2(arg1, arg2):
    print(f"hello, f2 {arg1}")
    for i in range(10):
        task_queue.put((f3, arg2, i))


def f1(arg1, arg2, arg3):
    print(f"hello, f1 {arg1}")
    for i in range(10):
        task_queue.put((f2, arg2, arg3))


def pool_executor():
    while True:
        task = task_queue.get()
        if task is None:
            # sentinel to terminate
            return

        fn, *args = task
        fn(*args)
        # Show this work has been completed:
        task_queue.task_done()


POOL_SIZE = 16

with concurrent.futures.ThreadPoolExecutor(POOL_SIZE) as executor:
    for _ in range(POOL_SIZE):
        executor.submit(pool_executor)

    for i in range(10):
        task_queue.put((f1, i, 1, 2))

    # Wait for all tasks to complete
    task_queue.join()
    # Now we need to terminate the running pool_executor tasks:
    # Add sentinels:
    for _ in range(POOL_SIZE):
        task_queue.put(None)

Prints:

hello, f1 0
hello, f1 1
hello, f1 3
hello, f1 5
hello, f1 7
hello, f1 9
hello, f1 2
hello, f2 1
hello, f2 1
hello, f2 1
hello, f1 4
hello, f1 6
hello, f1 8
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1
hello, f2 1

...

hello, f3, 2, 1, task_number = 992
hello, f3, 2, 2, task_number = 993
hello, f3, 2, 4, task_number = 995
hello, f3, 2, 6, task_number = 997
hello, f3, 2, 8, task_number = 999
hello, f3, 2, 3, task_number = 994
hello, f3, 2, 7, task_number = 998
hello, f3, 2, 5, task_number = 996
hello, f3, 2, 9, task_number = 1000

Perhaps you should consider creating your own thread pool with dameon threads, which will terminate when the main process terminates (you could still use the technique of adding sentinel values to signal these threads to terminate when we no longer require them in which case the threads need not be daemon threads).

from queue import Queue
from threading import Lock, Thread

...

def pool_executor():
    while True:
        fn, *args = task_queue.get()
        fn(*args)
        # Show this work has been completed:
        task_queue.task_done()


POOL_SIZE = 16

for _ in range(POOL_SIZE):
    Thread(target=pool_executor, daemon=True).start()

for i in range(10):
    task_queue.put((f1, i, 1, 2))

# Wait for all tasks to complete
task_queue.join()

A New Type of Multithreading Pool

We can abstract a multithreading pool that allows running tasks to continue to arbitrarily submit additional tasks and then be able to wait for all tasks to complete. That is, we wait until the task queue has quiesced, the condition where the task queue is empty and no new tasks will be added because there are no tasks currently running:

from queue import Queue
from threading import Thread

class ThreadPool:
    def __init__(self, pool_size):
        self._pool_size = pool_size
        self._task_queue = Queue()
        self._shutting_down = False
        for _ in range(self._pool_size):
            Thread(target=self._executor, daemon=True).start()

    def __enter__(self):
        return self

    def __exit__(self, exc_type, exc_val, exc_tb):
        self.shutdown()

    def _terminate_threads(self):
        """Tell threads to terminate."""
        # No new tasks in case this is an immediate shutdown:
        self._shutting_down = True

        for _ in range(self._pool_size):
            self._task_queue.put(None)
        self._task_queue.join()  # Wait for all threads to terminate


    def shutdown(self, wait=True):
        if wait:
            # Wait until the task queue quiesces (becomes empty).
            # Running tasks may be continuing to submit tasks to the queue but
            # the expectation is that at some point no more tasks will be added
            # and we wait for the queue to become empty:
            self._task_queue.join()
        self._terminate_threads()

    def submit(self, fn, *args):
        if self._shutting_down:
            return
        self._task_queue.put((fn, args))

    def _executor(self):
        while True:
            task = self._task_queue.get()
            if task is None:  # sentinel
                self._task_queue.task_done()
                return
            fn, args = task
            try:
                fn(*args)
            except Exception as e:
                print(e)
            # Show this work has been completed:
            self._task_queue.task_done()

###############################################

from threading import Lock

lock = Lock()

task_number = 0

results = []

def f3(arg1, arg2):
    global task_number

    with lock:
        task_number += 1
        n = task_number

    #print(f"hello, f3, {arg1}, {arg2}, task_number = {n}")
    results.append(f"hello, f3, {arg1}, {arg2}, task_number = {n}")


def f2(arg1, arg2):
    for i in range(10):
        pool.submit(f3, arg2, i)

def f1(arg1, arg2, arg3):
    for i in range(10):
        pool.submit(f2, arg2, arg3)


with ThreadPool(16) as pool:
    for i in range(10):
        pool.submit(f1, i, 1, 2)

for result in results:
    print(result)

Another Way That Uses Standard concurrent.futures Methods

As you have observed, in the above solution an f1 task will complete before the f2 tasks it has submitted has completed and f2 tasks will terminate before f3 tasks have terminated. The problem with your original code was due to a shutdown being implicitly called before all 1000 f3 tasks were submitted. We can prevent this premature shutdown from occuring by having each worker function return a list of Future instance whose results we await:

from concurrent.futures import ThreadPoolExecutor, Future
from threading import Lock

task_number = 0

lock = Lock()

futures = []

def f3(arg1, arg2):
    global task_number

    with lock:
        task_number += 1
        n = task_number

    print(f"hello, f3, {arg1}, {arg2}, f3 tasks started = {n}")


def f2(arg1, arg2):
    print(f"hello, f2 {arg1}")
    futures.extend(
        executor.submit(f3, arg2, i)
        for i in range(10)
    )


def f1(arg1, arg2, arg3):
    print(f"hello, f1 {arg1}")
    futures.extend(
        executor.submit(f2, arg2, arg3)
        for i in range(10)
    )


with ThreadPoolExecutor(16) as executor:
    futures.extend(
        executor.submit(f1, i, 1, 2)
        for i in range(10)
    )

    cnt = 0
    for future in futures:
        future.result()
        cnt += 1
    print(cnt, 'tasks completed.')

Prints:

...
hello, f3, 2, 4, f3 tasks started = 995
hello, f3, 2, 6, f3 tasks started = 997
hello, f3, 2, 8, f3 tasks started = 999
hello, f3, 2, 3, f3 tasks started = 994
hello, f3, 2, 7, f3 tasks started = 998
hello, f3, 2, 5, f3 tasks started = 996
hello, f3, 2, 9, f3 tasks started = 1000
1110 tasks completed.
2 of 3
0

Looks like, in your first example, maybe the program terminates before the "f2" thread gets its chance to print.

Adding a time.sleep call to the very end of your first example allows it to print both "hello" messages when I run it.*

import concurrent.futures
import time

def f2():
    print("hello, f2")


def f1():
    print("hello, f1")
    executor.submit(f2)


with concurrent.futures.ThreadPoolExecutor(16) as executor:
    executor.submit(f1)
    time.sleep(3)

I have not ever used concurrent.futures. Are its worker threads daemons?†


Update:

I wonder why main thread cannot find the f2 future...

Not sure what you're asking, but try this:

import concurrent.futures
import queue

q = queue.Queue(2)

def f2():
    print("hello, f2")

def f1():
    print("hello, f1")
    future_2 = executor.submit(f2)
    q.put(future_2)

with concurrent.futures.ThreadPoolExecutor(16) as executor:
    future_1 = executor.submit(f1)
    future_2 = q.get()
    future_1.result()
    future_2.result()

* Python 3.12.4 running on macOS Sonoma 14.4.1.

† I can't find "daemon" or "demon" anywhere in The documentation, and I can't find out by using Threading.current_thread().daemon because the current_thread function only works in threads that were created directly by the Threading module. current_thread returns a bogus object when called by a concurrent.futures worker thread.

Top answer
1 of 2
2

Here is the map version of your existing code. Note that the callback now accepts a tuple as a parameter. I added an try\except in the callback so the results will not throw an error. The results are ordered according to the input list.

from concurrent.futures import ThreadPoolExecutor
import urllib.request

URLS = ['http://www.foxnews.com/',
        'http://www.cnn.com/',
        'http://www.wsj.com/',
        'http://www.bbc.co.uk/',
        'http://some-made-up-domain.com/']

# Retrieve a single page and report the url and contents
def load_url(tt):  # (url,timeout)
    url, timeout = tt
    try:
      with urllib.request.urlopen(url, timeout=timeout) as conn:
         return (url, conn.read())
    except Exception as ex:
        print("Error:", url, ex)
        return(url,"")  # error, return empty string

with ThreadPoolExecutor(max_workers=5) as executor:
    results = executor.map(load_url, [(u,60) for u in URLS])  # pass url and timeout as tuple to callback
    executor.shutdown(wait=True) # wait for all complete
    print("Results:")
for r in results:  # ordered results, will throw exception here if not handled in callback
    print('   %r page is %d bytes' % (r[0], len(r[1])))

Output

Error: http://www.wsj.com/ HTTP Error 404: Not Found
Results:
   'http://www.foxnews.com/' page is 320028 bytes
   'http://www.cnn.com/' page is 1144916 bytes
   'http://www.wsj.com/' page is 0 bytes
   'http://www.bbc.co.uk/' page is 279418 bytes
   'http://some-made-up-domain.com/' page is 64668 bytes
2 of 2
1

Without using the map method, you can use enumerate to build the future_to_url dict with not just the URLs as values, but also their indices in the list. You can then build a dict from the future objects returned by the call to concurrent.futures.as_completed(future_to_url) with indices as the keys, so that you can iterate an index over the length of the dict to read the dict in the same order as the corresponding items in the original list:

with concurrent.futures.ThreadPoolExecutor(max_workers=5) as executor:
    # Start the load operations and mark each future with its URL
    future_to_url = {
        executor.submit(load_url, url, 60): (i, url) for i, url in enumerate(URLS)
    }
    futures = {}
    for future in concurrent.futures.as_completed(future_to_url):
        i, url = future_to_url[future]
        futures[i] = url, future
    for i in range(len(futures)):
        url, future = futures[i]
        try:
            data = future.result()
        except Exception as exc:
            print('%r generated an exception: %s' % (url, exc))
        else:
            print('%r page is %d bytes' % (url, len(data)))
🌐
Medium
medium.com › @smrati.katiyar › introduction-to-concurrent-futures-in-python-009fe1d4592c
Introduction to concurrent.futures in Python | by smrati katiyar | Medium
September 30, 2024 - import concurrent.futures import time import requests # Function to download a webpage def download_page(url): response = requests.get(url) return f"{url} - {len(response.content)} bytes" # List of URLs to download urls = [ "https://www.example.com", "https://www.python.org", "https://www.github.com", ] # Using ThreadPoolExecutor to download pages concurrently start_time = time.time() with concurrent.futures.ThreadPoolExecutor() as executor: futures = [executor.submit(download_page, url) for url in urls] for future in concurrent.futures.as_completed(futures): print(future.result()) end_time = time.time() print(f"Downloaded all pages in {end_time - start_time:.2f} seconds")
🌐
Super Fast Python
superfastpython.com › home › tutorials › how to use threadpoolexecutor submit()
How to use ThreadPoolExecutor submit() - Super Fast Python
August 3, 2023 - You can issue one-off tasks to the ThreadPoolExecutor using the submit() method. This returns a Future object that gives control over the asynchronous task executed in the thread pool.
🌐
GitHub
github.com › Python-Tools › asyncio-executor
GitHub - Python-Tools/asyncio-executor: 协程执行器,起一个额外的线程执行事件循环,主线程则管理这个事件循环线程, 这个执行器不要用在协程中.
from concurrent.futures import as_completed import requests as rq from asyncio_executor import AsyncioExecutor def httpsync(url): req = rq.get(url) return len(req.text) with AsyncioExecutor() as executor: to_do = [] urls = ["https://github.com/", "https://docs.aiohttp.org/"] for i in urls: job = executor.submit(httpsync, i) to_do.append(job) for future in as_completed(to_do): res = future.result() print(res)
Starred by 7 users
Forked by 5 users
Languages   Python 43.2% | Makefile 29.9% | Batchfile 26.9% | Python 43.2% | Makefile 29.9% | Batchfile 26.9%
🌐
Heavy Watal
heavywatal.github.io › python › concurrent.futures
concurrent.futures: 並行処理 in Python - Heavy Watal
import os import concurrent.futures as confu # 呼び出し順に拾う with confu.ThreadPoolExecutor(max_workers=os.cpu_count()) as executor: futures = [executor.submit(target_func, x) for x in range(8)] (done, notdone) = confu.wait(futures) for future in futures: print(future.result()) # 終わったやつから拾う with confu.ThreadPoolExecutor(max_workers=os.cpu_count()) as executor: futures = [executor.submit(target_func, x) for x in range(8)] for future in confu.as_completed(futures): print(future.result())
🌐
GeeksforGeeks
geeksforgeeks.org › how-to-use-threadpoolexecutor-in-python3
How to use ThreadPoolExecutor in Python3 ? - GeeksforGeeks
July 4, 2024 - It must be called after executor.submit() and executor.map() method else it would throw RuntimeError.
🌐
ZetCode
zetcode.com › python › threadpoolexecutor
Python ThreadPoolExecutor - concurrency in Python with ThreadPoolExecutor
#!/usr/bin/python import requests import concurrent.futures import time def get_status(url): resp = requests.get(url=url) return resp.status_code urls = ['http://webcode.me', 'https://httpbin.org/get', 'https://google.com', 'https://stackoverflow.com', 'https://github.com', 'https://clojure.org', 'https://fsharp.org'] tm1 = time.perf_counter() with concurrent.futures.ThreadPoolExecutor() as executor: futures = [] for url in urls: futures.append(executor.submit(get_status, url=url)) for future in concurrent.futures.as_completed(futures): print(future.result()) tm2 = time.perf_counter() print(f'elapsed {tm2-tm1:0.2f} seconds') The program concurrently checks the HTTP status codes of multiple websites, demonstrating ThreadPoolExecutor's efficiency for I/O-bound tasks.