Date: 11/30/00
- Previous message: Ignatius Teo: "RE: [phplib] Server Side Include"
- In reply to: nathan r. hruby: "Re: [phplib] performance"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nathan,
> phplib-7.2a also used to leave tons of open connections laying around, if
> you have't, change up to 7.2c it should help the out of connection
> problems.
I'm using 7.2b. How stable is c? I actually just installed b 2-3 weeks
ago, and I would have used c, but from what I read it looked like b was
the better release in terms of stability/reliability.
> Also, make sure you're destroying and / or reusing db objects as
> opposed to just starting a new one every time you need db access.
> (destroying the object will release the connection back to php's
> conenction pool)
Right now we're not even using db objects. Most of the code is older so
we just use the PHP mysql_* functions. Can I still release connections
back to the pool?
> Also, you can also just up the mysql_max_connections limit in your
> php3.ini file to something more resonable. 100 seems low if you get even
> 20 percet of your traffic at one time (say early morning...)
I just checked the ini file and currently mysql_max_connections is set
to -1, which means there is no limit. If mysql_max_connections in
php3.ini is equal to max_connections (the MySQL parameter) then
theoretically there shouldn't be any problems or am I wrong? Do clients
just have to wait if there are currently mysql_max_connections or would
they get the "too many connections" error?
Thanks
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>
- Previous message: Ignatius Teo: "RE: [phplib] Server Side Include"
- In reply to: nathan r. hruby: "Re: [phplib] performance"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

