Best practice for AsyncClient usage across multiple unknown hosts

[abdhx]

Hi team 👋 ,

I have a use case where I need to make HTTP requests to about 10 different hosts, each host will receive many requests, but the hostnames are only known at runtime.

Should I use a single httpx.AsyncClient instance across all hosts, or is it better to create one client per host?
Are there any performance, connection pooling, or resource management considerations I should be aware of when dealing with multiple hosts concurrently in this way?

Many thanks

[lovelydinosaur]

Good question. Using a single client instance everywhere is a sensible approach.
The current default policy is to allow a maximum of 10 concurrent connections.

It might be that there's smarter policies we could have by default (for a future version) eg. an overall ratelimit perhaps?

[abdhx]

@lovelydinosaur thanks for the quick answer

For my use case, do you think it's a good idea to use a single client then increase its number of concurrent connections? Or to create multiple clients?

[lovelydinosaur]

Just use a single client and assume that's a sensible policy. You'll see timeouts if you're bumping into the limits.