requests-futures VS grequests

- https://github.com/ross/requests-futures

For the simple one-off case, check out requests-futures or requests-threads

Lately I tried https://github.com/ross/requests-futures and it is really nice little wrapper for requests library that makes it run asynchronous via thread pool. Worth checking out if you are already using requests lib.

requests-futures can handle that

Thank you, I didn’t know about this before. Looks like either requests-threads or requests-futures can do the job. Not sure how I can add async and await to the script above, I’ll tinker around with it later!

I found examples of running parallel async http requests using grequests, but in its GitHub page it recommends using requests-threads or requests-futures instead. Which of them would be the most straightforward tool for optimizing a sequence of GET requests against an API. Case scenario: API endpoint provides paginated responses. With first response, I get the total of itens, which allow me to prepare all the remaining urls. The API allows for 25 simultaneous requests from a single user session (JWT token).

I would suggest using a session in requests if you're not already but also to look at asyncio/aiohttp , requests-futures or requests-html which can be used asynchronously and is written by the author of the requests library.

I was thinking just an async request like this https://github.com/spyoungtech/grequests along with Twilio's built in monitoring on success/not success could do?

grequests https://github.com/spyoungtech/grequests

I found examples of running parallel async http requests using grequests, but in its GitHub page it recommends using requests-threads or requests-futures instead. Which of them would be the most straightforward tool for optimizing a sequence of GET requests against an API. Case scenario: API endpoint provides paginated responses. With first response, I get the total of itens, which allow me to prepare all the remaining urls. The API allows for 25 simultaneous requests from a single user session (JWT token).

I'd use an asynchronous programming package like grequests or Scrapy. Basically, store all the links you want to visit in a list then prepare them, send the requests, and then iterate over the content of the response. If the website needs JavaScript to then you can use requests-html with AsyncHTMLSession to render the JavaScript. ``` import grequests

This video demonstrates Hosting FastAPI on Azure VM with Ubuntu. There are many factors to take into consideration on RAM and bandwidth. But to help you analyze the performance of your deployment, you can use grequests.

If you're doing something in a view that is i/o bound, doesn't take very long, and you need to do a lot of it in parallel (eg. hit 10 different API endpoints in parallel) then you might use threads, or something like this to speed up your view. You can also use an offine task framework like Celery in these cases as well.