I am also looking into pooling options for the same
reasons. Since we also will be using it for content management, we have
a caching mechanism in place. One of the options we thought of using was
having an second apache instance running that accepts all of the dynamic
requests and only has one process. So the 75-100 processes would be
serving cached pages, but when a cache hit occured, it would pass it off
to the other apache instance running only one process.
We probably won't do this, but it seems to be a viable option. We are
looking into pooling applications as alternatives.
Shaun
On Fri, 9 Feb 2001, John Donagher wrote:
>
> Mathijs-
>
> It would seem that a better model is to simply state that there are resources
> that would like to be persisted outside of PHP threads of execution, possibly
> outside of a webserver's process space, perhaps even outside of a physical
> machine or network. Many people will agree with you.
>
> What you're looking for would fall under the scope of an application server.
> You can find past discussions on this about that, from people who know far
> more about it than I do :)
>
> John
>
> On Sat, 10 Feb 2001, Mathijs Brands wrote:
>
> > Hi all,
> >
> > This is my first post to this list, so please bear with me ;)
> >
> > Anyway, I've been running/developing a PHP application (fairly simple
> > content management system) for some time now and it has been running
> > pretty well. I'm using Apache 1.3.14, PHP 3.0.16 and PostgreSQL 6.5.3.
> >
> > The problem is that the increasing number of requests the application
> > needs to service requires me to increase the number of Apache processes,
> > which sometimes causes database problems. Originally I had about 10-20
> > running processes, but now I sometimes reach 75-100 or more. Since I'm
> > using persistant db connections, this means I can have 100 (or more)
> > open db connections; this is not something PostgreSQL really likes.
> >
> > If I use normal db connections, everything works ok, but the performance
> > is no longer acceptable. I suspect that I only need 2-3 db connections
> > for every 10 running processes.
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
