From owner-freebsd-questions Mon Oct 28 14:21:50 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07565 for questions-outgoing; Mon, 28 Oct 1996 14:21:50 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA07552 for ; Mon, 28 Oct 1996 14:21:40 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id RAA00804; Mon, 28 Oct 1996 17:21:25 -0500 (EST) From: "John S. Dyson" Message-Id: <199610282221.RAA00804@dyson.iquest.net> Subject: Re: server death when swap space is all gone. To: robh@imdb.com Date: Mon, 28 Oct 1996 17:21:25 -0500 (EST) Cc: freebsd-questions@freebsd.org In-Reply-To: <199610282201.WAA10772> from "Rob Hartill" at Oct 28, 96 10:01:46 pm Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I know linux is crap, but the simple fact is my 96Mb FreeBSD machine > with 77Mb of swap, doing nothing but "diff" on two files falls over > with "diff: memory exhausted", while a 48mb linux machine with ? swap > can produce the 700k diff file. > Ahhh.... I thought that you had problems with swap space :-). Nahhh, we just normally use an arbitrary memory limit of 64MB per proc, easily upgraded to 128MB by a bash command like: ulimit -d 131000 > > When I run diff, "top" shows no evidence that the swap is being used or > that 'cache' memory being reclaimed. The process grows to 33Mb then reports > "diff: memory exhausted". > Yep, I'll bet you that it is the above... > > I think we tried this once on a FreeBSD machine with far more swap and > it failed there too. > This isn't dependent on VM system, as much as an administrative limit. > > Why does the FreeBSD's superior memory management let me down ? > It is an administrative limit :-). John