Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Nov 1998 16:43:44 +0100
From:      Eivind Eklund <eivind@yes.no>
To:        Barrett Richardson <terbart@aye.net>, garman@earthling.net
Cc:        current@FreeBSD.ORG
Subject:   Re: more dying daemons
Message-ID:  <19981121164344.E17306@follo.net>
In-Reply-To: <Pine.BSF.3.96.981121025345.26942A-100000@phoenix.aye.net>; from Barrett Richardson on Sat, Nov 21, 1998 at 03:09:13AM -0500
References:  <199811210418.UAA06160@hub.freebsd.org> <Pine.BSF.3.96.981121025345.26942A-100000@phoenix.aye.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 21, 1998 at 03:09:13AM -0500, Barrett Richardson wrote:
> 
> 
> On Fri, 20 Nov 1998 garman@earthling.net wrote:
> 
> > On 20 Nov, Barrett Richardson wrote:
> > > 
> > > Swap usage at 64% after only hour seems awfully high. I've seem similar
> > > behaviour in the world of SCO. Folks just under the threshold of what
> > > they can get out of their box with given swap/memory size with 3.2v4.2
> > > are having no problems. They upgrade to Open Server 5, put the same load
> > > on it, and the box starts a slow downward spiral and finally becomes
> > > unusable. They reboot it, and its ok for a couple of hours.
> > > 
> > The 64% swap usage figure was from an uptime of two days, not an hour. 
> > I have however easily produced swap usages around 56-58% (synthetically,
> > of course) within 10-20 minutes while testing some of the potential
> > fixes posted here.
> > 
> > i've never had a problem with insufficient swap before...
> 
> The resource requirements for -current may be a tad higher than
> for -stable. Like I mentioned earlier you may have been running
> just under the threshold with your previous configuration.

The bug in question is "new" (23rd february, most likely), and is not
visible in -stable.  It is a serious bug.  Saying that his swap usage
is 'too high' is not going to help us solve it; the system is supposed
to be stable no matter what.  We can't take 3.0 to be -STABLE until
this bug and the clock bug is solved.

Eivind.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981121164344.E17306>