Thanks for the reply!, Scott! I considered changing the number of
allowed connections but I figured this would just defer the problem,
as the root problem was the increasing number of connections.
Last night I went through the entire website looking for code that
used mysql_pconnect() in
That's very odd... Technically pconnect should be a lot faster, not sure
exactly why it's not. The other thing you might want to look at is the
MySQL idle timeout (or something like that). That's how long your
pconnects stay connected if they don't transfer any traffic. I think it
At 9:35 AM -0700 5/3/01, Scott Baker wrote:
That's very odd... Technically pconnect should be a lot faster, not
sure exactly why it's not. The other thing you might want to look
at is the MySQL idle timeout (or something like that). That's how
long your pconnects stay connected if they
Repost - nobody has any ideas? I've run some stress tests, sending
several thousand page requests, and the number of mysql processes
goes up and down but over time continues to rise. It's up to about
22 now. When it gets to about 30, every request from the web server
will be will fail.
You can look into increasing the number of allowed connections that MySQL
will accept... are you using connect or pconnect?
At 04:23 PM 5/3/2001 -0700, Gary Bickford wrote:
Repost - nobody has any ideas? I've run some stress tests, sending
several thousand page requests, and the number of
I am running MySQL (3.23.27 at this point) with Apache1.3.12 and PHP3 on
a PC running Redhat 6.0. My problem has survived upgrades of all
components from earlier versions.
Every PHP page has at least one query to a MySQL database for session
tracking (home-rolled code, not PHPLib or anything
