[dev] Reducing persistent database connections

[Joe Wilson]

I think that the best way to do this would be to have the framework set up a
connection pool that the individual apps can request from.  This way, you
configure Horde to initialize with X persistent connections, allow it to grow
to a maximum of Y connections.  This avoids the overhead of creating a
connection on each app request, which will get very expensive very quickly, 
while still optimizing the use of connections.

I have to admit, though, that I am sufficiently ignorant of PHP state management
that I do not know whether shared resources across Apache child processes is
supported.

Regards,

Joe

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jon Parise <jon at horde.org>:
>
> > I'd like to alter all of our applications to _not_ request persistent
> > connections and make it a rule that persistent connections only be
> > requested by the Horde Framework itself and not by applications (at
> > least in the default configuration).
> >
> > Comments on this?
>
> I think largely it makes sense. Why do you want to keep them by default in
> the framework, though? Doesn't the same logic apply?
>
> I'd like to see this be a config setting for persistent or no, and I'm fine
> with us defaulting it to no.
>
> -chuck
>
> --
> Charles Hagenbuch, <chuck at horde.org>
> The alligators were there, too, in a bathtub inside the house.
>
>
> --
> Horde developers mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>