From owner-freebsd-current Sat Nov 21 07:44:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20347 for freebsd-current-outgoing; Sat, 21 Nov 1998 07:44:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20326 for ; Sat, 21 Nov 1998 07:44:18 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA16177; Sat, 21 Nov 1998 16:43:46 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA23684; Sat, 21 Nov 1998 16:43:45 +0100 (MET) Message-ID: <19981121164344.E17306@follo.net> Date: Sat, 21 Nov 1998 16:43:44 +0100 From: Eivind Eklund To: Barrett Richardson , garman@earthling.net Cc: current@FreeBSD.ORG Subject: Re: more dying daemons References: <199811210418.UAA06160@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Barrett Richardson on Sat, Nov 21, 1998 at 03:09:13AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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