I have tried to figure out exact relationship between settings that limit
per-connection manager number of connections: maximum connections to
open/retain per-host, and max connections overall.
I read documentation on web site, apologies if I missed an obvious answer.
Specifically, I am trying to figure out whether there is any difference between
using persistent connections and not. Right now I assume there is no difference
-- persistent connections are just held onto in hopes they may be reused, but
either way, these are hard limits for all connections (per-host and total).
But what I really would be able to figure out is this: is there a way to limit
number of persistent (keep-alive) connections to lower value than hard-limit on
number of connections that can be opened?
Basically so that limit to check against when opening a connection would be
higher (say, 10), but limit to check when deciding whether client will keep the
connection would be lower (say, 2). This would allow for temporary opening of
higher number of concurrent connections during load spikes, without leaving
higher number of open connections.
I guess alternative way would be to just use aggressive values for closing free
open connections.
I appreciate any suggestions,
-+ Tatu +-
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
