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
Hello Ron,
On 11-Feb-01 20:48:54, you wrote:
>There are some people out there working on different multiplexors
>and db pool mechanisms for PHP, look in the archives for "application
>server", "connection pooling", etc. But you may find that simply killing
>off your processes sooner may do just
Mathijs Brands wrote:
> 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
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.
Wh
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
