From owner-freebsd-questions@FreeBSD.ORG Mon Jul 5 03:54:45 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB1BD16A4CE for ; Mon, 5 Jul 2004 03:54:45 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A86AD43D60 for ; Mon, 5 Jul 2004 03:54:45 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (rwcrmhc11) with ESMTP id <2004070503544401300jamtme>; Mon, 5 Jul 2004 03:54:45 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id D12C874; Sun, 4 Jul 2004 23:54:43 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Lists To: freebsd-questions@freebsd.org References: <71704ff3727060e5144ffddc6ee8daed@159.148.60.10> From: Lowell Gilbert Date: 04 Jul 2004 23:54:43 -0400 In-Reply-To: <71704ff3727060e5144ffddc6ee8daed@159.148.60.10> Message-ID: <44vfh39kho.fsf@be-well.ilk.org> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Swap size X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2004 03:54:46 -0000 Lists writes: > What swap size should i use having 768 Mb of memory? > I've heard something about preformance degradation if > swap size is bellow 2x of ram... You don't *need* ANY swap. Until you fill up your RAM, at which point it's nice to have some swap space instead of having the kernel start killing processes. In order to do a crash dump, you need an overwritable partition that's at least slightly larger than your RAM. The swap partition is often given this job as well as serving as swap space. If you have some idea of your worst-case virtual memory usage, allocate that much swap (less about the amount of RAM you have). If you don't know, either set aside a huge amount of space or experiment and see how much you need (and then allocate half again as much to be safe).