From owner-freebsd-isp@FreeBSD.ORG  Sun Apr  6 23:47:56 2003
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A262E37B413; Sun,  6 Apr 2003 23:47:55 -0700 (PDT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 97BEC43FB1; Sun,  6 Apr 2003 23:47:54 -0700 (PDT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 8371672E7C; Sun,  6 Apr 2003 23:47:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 8201672E74; Sun,  6 Apr 2003 23:47:54 -0700 (PDT)
Date: Sun, 6 Apr 2003 23:47:54 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Mattias Pantzare <pantzer@ludd.luth.se>
In-Reply-To: <3E90835F.9020104@ludd.luth.se>
Message-ID: <20030406234549.C54715@carver.gumbysoft.com>
References: <20030406120112.I11095-100000@netmint.com>
	<3E906828.8060001@mac.com> <3E90835F.9020104@ludd.luth.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-isp@freebsd.org
cc: Support <support@netmint.com>
cc: freebsd-stable@freebsd.org
Subject: Re: load testing and tuning a 4GB RAM server
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2003 06:47:56 -0000

On Sun, 6 Apr 2003, Mattias Pantzare wrote:

>
> > The notion of tuning kernel variables to the amount of memory on the
> > _build_ system-- which is not always the same as the system which will
> > be running the kernel-- doesn't strike me as the right thing to do, so I
> > tend to set this to 64 or so by default, and then change it on a
> > case-by-case basis as the need arises.
>
> That is why maxusers 0 will auto-size when the kernel _boots_. Not at
> buildtime.

.. unfortunately 'maxusers 0' on >2GB systems causes the tables to get
*too* big, and you can easily deplete KVM in this instance. Check the
archives for the discussion-of-the-month about this.

I'd suggest maxusers 128 and tune other items as needed, particuarly the
tunables kern.ipc.nmbclusters and kern.ipc.nmbufs.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org