Thanks. My problem is that I am getting a "too many connections" error, and wondered if there was a proper configuration to handle this. I have the problem, regardless of using connect or pconnect. I originally used pconnect for the last year. But my site is growing and growing and am looking for anything to help fix the problem. So I switched to connect, with no luck in fixing the "too many connections" problem. Originallly, increasing max_connections in my.cnf solved the problem for a while. But the growth has caught up again.
I thought I read that increasing this max_connections number too high could cause problems as well. So I am hesitant to raise it anymore. -- Nicole aeontrek.com "Jason Sheets" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Generally persistent connections will almost always be faster there are > some considerations though, first resource usage if you are busy site > and don't have enough memory to support one connection to the db for > each apache process you will run into problems, second if you site is > not busy enough and you rarely connect to the database you wont see much > of a performance increase. Sometimes you need to take precautions to > safely restart apache otherwise you can have connections to the db left > open. > > Obviously persistent connections are faster because you don't have the > overhead of building and tearing down the connection on each request, > I've seen a 5 to 15% increase in page generation time on some > applications by using persistent connections depending on the db server > and the protocol. > > Becoming Digital wrote: > > >I'm with Chris on this one. I did some serious load testing on my servers and always faired better with persistent connections. I don't have the logs handy right now, but I can probably dig them up if anyone really wants to see the numbers. > > > >Edward Dudlik > >Becoming Digital > >www.becomingdigital.com > > > > > > > >----- Original Message ----- > >From: "Chris Shiflett" <[EMAIL PROTECTED]> > >To: "Curt Zirzow" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > >Sent: Wednesday, 01 October, 2003 22:53 > >Subject: Re: [PHP] "Too many connections" fix? > > > > > >--- Curt Zirzow <[EMAIL PROTECTED]> wrote: > > > > > >>This may be debatable, which is better? php searching through a > >>pool of 1000 connections for a free one or the overhead of opening > >>a new resource to the database each request. > >> > >> > > > >I suppose people can debate just about anything, but I doubt anyone can come up > >with any statistics to defend the stance that persistent connections are slower > >under heavy traffic. Of course, I'd love to see people's results, but my > >experience has shown quite the opposite. > > > >Also, the difference becomes exaggerated with heavier traffic. So, a better > >argument would be to ask whether the overhead of managing persistent > >connections is worth it when you only have one database connection per hour. In > >that case, it may actually be worse, but that's not the situation that was > >described. :-) > > > >Hope that helps. > > > >Chris > > > >===== > >RAMP - Rapid AMP Training from the Experts > > http://www.nyphp.org/content/training/ramp.php > >HTTP Developer's Handbook > > http://shiflett.org/books/http-developers-handbook > >My Blog > > http://shiflett.org/ > > > > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
