maxConnectionsPerRoute

maxConnectionsPerRoute is a configuration parameter used by HTTP client connection pools to bound the number of concurrent connections that can be opened to a single route, typically a host and port combination. A route represents a target endpoint; multiple routes can be active at the same time, subject to overall pool limits.

Rationale: Without a per-route limit, a client could exhaust system resources by opening many connections to one host, potentially starving other requests. Enforcing per-route limits helps ensure fairness and predictable performance, especially in high-concurrency scenarios and when servers have their own connection handling constraints.

Configuration: In most libraries this value is part of the connection pool configuration. It is commonly paired with a global maximum total connections to bound the overall pool size. The exact naming varies; terms such as defaultMaxPerRoute, maxPerRoute, or maxConnectionsPerRoute may be used, and the setting can be applied either per pool or globally. Users typically set a reasonable per-route limit and a separate total limit to balance throughput and resource usage.

Impact and tuning: Increasing the per-route limit can reduce latency for clients targeting the same host under heavy load, but it raises resource consumption and the risk of overwhelming a backend or exhausting file descriptors. Lower values improve fairness and resource usage but can increase waiting times. Tuning should be guided by workload characteristics, server capacity, and monitoring metrics like connection wait times, error rates, and throughput.

See also: connection pool, maxTotal, route, pool manager.