"Honza Novak" <kacerr(at)developers(dot)zlutazimnice(dot)cz> writes:
> Hi all,
> i'm looking for correct or at least good enough solution for use of multiple
> apaches with single postgres database. (apaches are 2.0.x, and postgres is
> At this moment i'm involved in management of a website where we have large user
> load on our web servers. Apaches are set up to be able to answer 300 requests
> at the same time and at the moment we have 4 apaches.
Do you have 300 processors? Are your requests particularly i/o-bound? Why
would running 300 processes simultaneously be faster than running a smaller
number sequentially? It doesn't sound like your systems are capable of
handling such a large number of requests simultaneously.
The traditional answer is to separate static content such as images which are
more i/o-bound onto a separate apache configuration which has a larger number
of connections, limit the number of connections for the cpu-bound dynamic
content server, and have a 1-1 ratio between apache dynamic content
connections and postgres backends. The alternative is to use connection
pooling. Often a combination of the two is best.
In response to
pgsql-performance by date
|Next:||From: Giulio Cesare Solaroli||Date: 2007-10-24 13:37:07|
|Subject: Re: Finalizing commit taking very long|
|Previous:||From: Tom Lane||Date: 2007-10-24 13:15:56|
|Subject: Re: Finalizing commit taking very long |