From owner-freebsd-current  Thu Feb  5 14:40:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA14012
          for current-outgoing; Thu, 5 Feb 1998 14:40:33 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA13758
          for <current@FreeBSD.ORG>; Thu, 5 Feb 1998 14:38:54 -0800 (PST)
          (envelope-from kkennawa@physics.adelaide.edu.au)
Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA24470; Fri, 6 Feb 1998 09:08:34 +1030
Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
	id AA22995; Fri, 6 Feb 1998 09:09:44 +1030
Date: Fri, 6 Feb 1998 09:09:43 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: Eivind Eklund <eivind@yes.no>
Cc: Mark Mayo <mark@vmunix.com>, current@FreeBSD.ORG
Subject: Re: Any feedback on my recent kernel 'fixes'
In-Reply-To: <19980205194454.64968@follo.net>
Message-Id: <Pine.OSF.3.90.980206090454.18894A-100000@bragg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current"

On Thu, 5 Feb 1998, Eivind Eklund wrote:

> On Wed, Feb 04, 1998 at 11:59:10PM -0500, Mark Mayo wrote:
> > Well, I just cvsup'ed and have been pounding my box with "real world"
> > workstation type use.. I have 32MB of RAM, and I ran several
> > copies of Netscape,
> 
> Hey - which Netscape?  I've got 64M and 141M swap, and I'm getting
> 'out of swap space' _often_ with just a single Netscape 4.04 and a
> couple of Netscape-windows.

Netscape 4.04 seems to handle memory caching of webpages _woefully_. 
Whenever I run NS4 with a memory cache size set above 0, it invariably 
dies after an hour of browsing or less, complaining about being out of 
memory (despite the fact that free swap space remains on the machine). 
This problem was noticed by others some time late last year, and since 
then I had been running with memory (and disk) caches set to 0kb (and 
pointing my browser to an apache web-cache I installed locally) but when 
I recently gave it some of its' own memory cache again I'm seeing the 
same thing.

I'd be interested to hear of any other fixes to this problem which dont 
impact so much on performance (perhaps it's just the way I've got apache 
set up, but I dont get all that stunning performance from the cache :)

Kris