The soft load shedding idea is great.
Along the lines of "lots of idle connections" is the issue with the simple
number of connections. I suspect in most real world apps you'll have
logic+web serving on a set of frontends talking to a single db backend
(until clustering is really nailed).
The is
On Tue, 24 Apr 2001, Nathan Myers wrote:
> On Tue, Apr 24, 2001 at 11:28:17PM -0300, The Hermit Hacker wrote:
> > I have a Dual-866, 1gig of RAM and strip'd file systems ... this past
> > week, I've hit many times where CPU usage is 100%, RAM is 500Meg free and
> > disks are pretty much sitting i
On Tue, Apr 24, 2001 at 11:28:17PM -0300, The Hermit Hacker wrote:
> I have a Dual-866, 1gig of RAM and strip'd file systems ... this past
> week, I've hit many times where CPU usage is 100%, RAM is 500Meg free and
> disks are pretty much sitting idle ...
Assuming "strip'd" above means "striped",
On Tue, Apr 24, 2001 at 12:39:29PM +0800, Lincoln Yeoh wrote:
> At 03:09 PM 23-04-2001 -0300, you wrote:
> >Basically, if great to set max clients to 256, but if load hits 50
> >as a result, the database is near to useless ... if you set it to 256,
> >and 254 idle connections are going, load won
At 03:09 PM 23-04-2001 -0300, you wrote:
>
>Anyone thought of implementing this, similar to how sendmail does it? If
>load > n, refuse connections?
>
>Basically, if great to set max clients to 256, but if load hits 50 as a
>result, the database is near to useless ... if you set it to 256, and 254
