What is the best way to send multiple HTTP requests in Python 3?
Since you're using python 3.3, I'll recommend a python3-only stdlib solution: concurrent.futures
.
This is a higher-level interace than just dealing directly with threading
or multiprocessing
primitives. You get an Executor
interface to handle pooling and asynchronous reporting.
The docs have an example that is basically directly applicable to your situation, so I'll just drop it here:
import concurrent.futures
import urllib.request
URLS = #[some list of urls]
# Retrieve a single page and report the url and contents
def load_url(url, timeout):
conn = urllib.request.urlopen(url, timeout=timeout)
return conn.readall()
# We can use a with statement to ensure threads are cleaned up promptly
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): url for url in URLS}
for future in concurrent.futures.as_completed(future_to_url):
url = future_to_url[future]
try:
data = future.result()
# do json processing here
except Exception as exc:
print('%r generated an exception: %s' % (url, exc))
else:
print('%r page is %d bytes' % (url, len(data)))
You can replace urllib.request
calls with requests
calls, if you so desire. I do tend to like requests
more, for obvious reasons.
The API goes a little bit like this: make a bunch of Future
objects that represent the asynchronous execution of your function. You then use concurrent.futures.as_completed
to give you an iterator over your Future
instances. It will yield them as they are completed.
As for your question:
Also, is there a rule of thumb to figure out the optimal number of threads as a function of the number of requests, is there any?
Rule of thumb, no. It depends on too many things, including the speed of your internet connection. I will say it doesn't really depend on the number of requests you have, more on the hardware you're running on.
Fortunately it is quite easy to tweak up the max_workers
kwarg and test for yourself. Start at 5 or 10 threads, ramp up in increments of 5. You'll probably notice performance plateauing at some point, and then start to decrease as the overhead of adding additional threads overtakes the marginal gain of increased parallelization (which is a word).
Nikolay Derkach
I am a product-focused developer and iOS expert with over six years of industry experience and a security background. I've worked extensively on building iOS apps and product MVPs for a wide range of clients, with additional advisory on product strategy and UX design. My passion is to work with startups to bring the first iteration of a product to market. Much of my work experience is remote, and I have developed effective communication skills through collaborating with international teams. I have also served as a technical screener for Toptal, and have led interviews for hundreds of talented developers from around the world. In addition to my experience I hold advanced degrees in Electrical Engineering and Applied Mathematics from Bauman Moscow State University.
Updated on July 24, 2022Comments
-
Nikolay Derkach almost 2 years
The idea is simple: I need to send multiple HTTP requests in parallel.
I've decided to use requests-futures library for that, which basically spawns multiple threads.
Now, I have about 200 requests and it's still pretty slow (takes about 12 seconds on my laptop). I'm also using a callback to parse the response json (as suggested in the library documentation). Also, is there a rule of thumb to figure out the optimal number of threads as a function of the number of requests, is there any?
Basically, I was wondering if I can speed up those requests any further.
-
BenDundee over 10 yearsLet me say, there are limitations about open threads that I've run into before on our AWS machines, but not on my laptop. The issue is outlined here: alak.cc/2011/11/python-threaderror-cant-start-new.html
-
Nikolay Derkach over 10 years@roippi have you had a look at requests-futures module I reverenced in my original post? It implements pretty much the same code.
-
roippi over 10 years@NikolayDerkach no I haven't, but looking at it.. huh! It wraps basically the above into one API call, which is quite nice. The one problem with that is that if it is slow/misbehaving, you don't have any recourse for fine-tuning it. You can more easily instrument the above code when stuff goes wrong, for example. Anyway, good luck :)