Anurag Agarwal created HTTPCORE-686:
---------------------------------------
Summary: Pre-init minimum number of connections
Key: HTTPCORE-686
URL: https://issues.apache.org/jira/browse/HTTPCORE-686
Project: HttpComponents HttpCore
Issue Type: New Feature
Components: HttpCore NIO
Reporter: Anurag Agarwal
Most of the applications suffer from a problem of cold start where we don't
have connections created at the start of the application and thus the first few
requests suffer by making a lot of connections.
During deployment this can even pile up a lot of not completed request and may
lead to losses.
One suggestion I had in mind is to create few connections before the
application has begun from the intended endpoints.
Also sometimes the nautre of your traffic can be spiky in which scenario
opening and closing a lot of connections also doesn't make sense.
These can be solved with either or both of the suggestions:
# Have a minConnectionPerHost policy in connection pool which won't let
connection pool for a host to go below this number or make a new connection
when it does. At the start of the http client these minimum connections will be
created to the end services.
# Provide an easy mechanism for use to create connections via
ConnectionManager. Currently in PoolingAsyncConnectionManager one must give
ConnectionInitiator which make it difficult to directly use the connection
manager to create connections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
