Nick,
--On 9 March 2012 19:20:17 + Nick Kew wrote:
if I have (say) 100 mpm-prefork workers, and 0.001%
of my queries are to the concerned (this ratio is
approximately correct numerically), I don't really want 100 database
connections constantly open, lasting for the life of the mpm-prefor
On Fri, 09 Mar 2012 16:37:44 +
Alex Bligh wrote:
> However, I /think/ it means that there is one connection per
> worker in a non-threaded environment still?
In a non-threaded environment, your choices are the two classic/
ancient models: original CGI (one connection per hit) and original
LA
Nick,
--On 9 March 2012 15:05:10 + Nick Kew wrote:
(I am running non-threaded due to various
legacy nonsense).
If you're running non-threaded then those DBD settings make
no sense: you need DBDMax of 1 and DBDMin of 0 or 1.
That's fine, I suppose, as far as it goes, and thank you
fo
On Fri, 09 Mar 2012 14:04:19 +
Alex Bligh wrote:
>(I am running non-threaded due to various
> legacy nonsense).
If you're running non-threaded then those DBD settings make
no sense: you need DBDMax of 1 and DBDMin of 0 or 1.
I suppose it's a buglet that mod_dbd only knows whether APR is
I have a busy websebserver with a configuration like this:
SSLEngine on
DocumentRoot /opt/busy
DBDriver pgsql
DBDParams "host=192.200.2.2 dbname=foo user=foo password=foo"
DBDMin 4
DBDKeep 8
DBDMax 20
DBDExptime 300
