I'm trying to improve upon a php-application for a client that utilises databases
heavily and as the number of users increase we've seen that the database is getting
really bogged down.
Many of these mysql sessions only does one or two queries, so I was thinking about
using mysql_pconnect and persistent connections rather than the ordinary
use-and-throw-away sessions.
Reading the comments in the manual there were conflicting views on whether or not
persistent links are more effective than the normal mysql links.
The database handling is done from a class (or actually multiple through inheritance)
and there are one comment in the manual that mentions problems with using pconnect
and multiple instances of a class, does anybody have info on this?
Basicly has anybody successfully improved upon mysql_connect by using
mysql_pconnect in busy applications (preferably through classes).
--
Andreas D Landmark / noXtension
Real Time, adj.:
Here and now, as opposed to fake time, which only occurs there
and then.