If my program connects only to a single origin, is there a difference between max_concurrent_requests and pool_options.max_connections_per_origin?

[alexeyr-ci]

The question is in the title.

[HoneyryderChuck]

Hi, "max connections per origin" will be the maximum number of connections, in a given pool/session, connecting to an origin, I.e. if you use the same session across N threads (sidekiq workers for example), and N > max connections per origin M, if at a given point M workers are busy waiting on a response from the origin, the M + 1 worker will wait for one of them to be released before proceeding (or time out is reached).

Max concurrent requests is for the number of simultaneous requests you can send at once on 1 connection; this only is taken into account if requests can be sent concurrently, I.e. in HTTP/2 they can be mhltiplexed, in HTTP/1 they can be pipelined.

Hope that clarifies.

[alexeyr-ci]

Thanks! Will sending multiple requests to a single origin in HTTP/2 always multiplex them on a single connection (assuming no max_concurrent_requests), or will multiple connections be used after some point?

[HoneyryderChuck]

If requests are sent in the same httpx request call, and origin/protocol allows, they will be multiplexed. Currently only single connection / origin multiplexing is supported, no more than a single connection per origin will be used at a given time per httpx request call.

[alexeyr-ci]

Thank you again!