Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 06 Apr 2003 21:53:54 +0200
From:      Mattias Pantzare <pantzer@ludd.luth.se>
To:        Support <support@netmint.com>
Cc:        freebsd-isp@freebsd.org
Subject:   Re: load testing and tuning a 4GB RAM server
Message-ID:  <3E9085D2.4020403@ludd.luth.se>
In-Reply-To: <20030406145845.R18790-100000@netmint.com>

index | next in thread | previous in thread | raw e-mail

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.


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E9085D2.4020403>