Date: Sat, 21 Nov 1998 03:09:13 -0500 (EST) From: Barrett Richardson <terbart@aye.net> To: garman@earthling.net Cc: current@FreeBSD.ORG Subject: Re: more dying daemons Message-ID: <Pine.BSF.3.96.981121025345.26942A-100000@phoenix.aye.net> In-Reply-To: <199811210418.UAA06160@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > > You can use vnconfig to test the beast without reslicing if you > > have ample disk space. > > > yes, but isn't this just a workaround? I rarely (if ever) run out of > memory and swap, and my usage usually stabilizes around 65% after a few > days. I still say 65% is high. I have never been able to get a box to run reliably for extended periods with swap usage above 50%. > > i would expect a system to behave reasonably even in the face of memory > shortages. corrupting running processes (when they fork?) is not a > reasonable behavior. There is a fairly recent thread about the low junk pointers in the archives. Might be some useful info there; ftp2.freebsd.org (or maybe ftp5, can't remember for sure) was afflicted with that problem for a day or so. > > > If problems persist, entertain the idea that something you > > are using has a mongo memory leak. > > > basically this is just my personal workstation box. whats > running include netscape, tkrat (with huge mailboxes :/), windowmaker, > and various other X apps. nothing particularly suspect (except perhaps > for netscape :)) > > enjoy > -- > Jason Garman http://garman.dyn.ml.org/ > Student, University of Maryland garman@earthling.net > And now... did you know that: Whois: JAG145 > "If you fart consistently for 6 years and 9 months, enough gas is > produced to create the energy of an atomic bomb." -- 0xdeadbeef posting > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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?Pine.BSF.3.96.981121025345.26942A-100000>