Mailing-List: contact modperl-help@apache.org; run by ezmlm
From: Vivek Khera <khera@kciLink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14932.41073.343134.777956@onceler.kciLink.com>
Date: Thu, 4 Jan 2001 11:10:25 -0500
To: modperl@apache.org
Subject: Re: the edge of chaos
In-Reply-To: <20010104023910.A14650@blue.dslreports.com>
References: <20010103222504.A1265@blue.dslreports.com>
	<20010103235717.A29114@buzzard.kdi.com>
	<20010104023910.A14650@blue.dslreports.com>

>>>>> "J" == Justin  <jb@dslreports.com> writes:

J> When things get slow on the back end, the front end can fill with
J> 120 *requests* .. all queued for the 20 available modperl slots..
J> hence long queues for service, results in nobody getting anything,

You simply don't have enough horsepower to serve your load, then.

Your options are: get more RAM, get faster CPU, make your application
smaller by sharing more code (pretty much whatever else is in the
tuning docs), or split your load across multiple machines.

If your front ends are doing nothing but buffering the pages for the
mod_perl backends, then you probably need to lower the ratio of
frontends to back ends from your 6 to 1 to something like 3 to 1.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/