From owner-freebsd-isp@FreeBSD.ORG Sun Apr 6 12:53:58 2003 Return-Path: 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 E2FA737B401 for ; Sun, 6 Apr 2003 12:53:58 -0700 (PDT) Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72C0443F85 for ; Sun, 6 Apr 2003 12:53:57 -0700 (PDT) (envelope-from pantzer@ludd.luth.se) Received: from ludd.luth.se (skalman.campus.luth.se [130.240.197.52]) by mother.ludd.luth.se (8.11.6+Sun/8.9.3) with ESMTP id h36Jrs818816; Sun, 6 Apr 2003 21:53:54 +0200 (MEST) Message-ID: <3E9085D2.4020403@ludd.luth.se> Date: Sun, 06 Apr 2003 21:53:54 +0200 From: Mattias Pantzare User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Support References: <20030406145845.R18790-100000@netmint.com> In-Reply-To: <20030406145845.R18790-100000@netmint.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-isp@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Apr 2003 19:53:59 -0000 Support wrote: > [..clip..] > > >>However, possibly with a degree of self-contradictory advice :-), I'd >>set maxusers to a specific value like 256 or so. > > > I will set it to 384 that the system already auto-defaults it to, unless > someone can suggest why I should leave it at 0. Perhaps you guys should > make it very clear in the manuals or LINT that autotuning only happens at > boot time because there possibly is a perception that it auto-tunes on a > running system. Even after I read all threads regarding this that I can > find, I am still not sure what sysctl vars will be able to auto-tune at > RUNTIME while the load creeps up. I am sure the important ones like > nmbclusters and n/mbuf variables can't. So which can? The sysctl vars that you can set will not auto-tune, that would be bad as that would destroy you setting. If a resource is auto-tuing then you set the limit with the sysctl. The autotuing of maxusers is based on your amount of RAM, that will not change while the system is running.