[dev] Reducing persistent database connections

[Joe Wilson]

Since, as Jan pointed out, PHP does not offer connection pooling or a single
connection per Apache process, I think you would be wise to test this on a
single application before altering the entire codebase.  Check before and after
on performance and # of connections used for that application.

I caution this because it isn't clear why connections to MySQL have become cheap
(as referred to in the LiveJournal.com document) or that this is generally true
for other DBs or languages.  LiveJournal.com runs mod_perl, not mod_php, and so
what is true for them may not be true for Horde.

Having spent the last seven years architecting and optimizing high-volume
database driven web applications, I have learned that this decision should be
made based upon empirical evidence as the situation is rarely as simple as it
seems.

Just my opinion.  I've had my say.  Thanks.  :p

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
>