Date: Sat, 31 Jan 2004 10:46:13 -0700 From: Scott Long <scottl@freebsd.org> To: Andy Hilker <ah@crypta.net> Cc: freebsd-current@freebsd.org Subject: Re: 5.2-RELEASE crash Message-ID: <401BE9E5.5050200@freebsd.org> In-Reply-To: <20040131173409.GA79338@mail.crypta.net> References: <20040130124818.T2246@gandalf.midgard.liu.se> <20040131003843.I10185@alpha.siliconlandmark.com> <401BD9D6.7020904@freebsd.org> <20040131173409.GA79338@mail.crypta.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Andy Hilker wrote: > Hi, > > >>Also, the scaling of kern.maxvnodes doesn't work very well. On a large >>memory system, it will typically set this to 200,000-300,000. If you >>don't need this many, then it is easier to just crank it down to a more >>reasonable level than fiddle with the KMEM parameters. > > > And what is reasonable level or how i determine it? :) > > Andy > Look at what you are doing with your system. If you're serving a high-traffic website with hundreds of thousands of files, you might not want to lower the maxvnode limit. If you're only dealing with a small working set of files that only spikes occasionally, lowering the limit is probably a good thing. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?401BE9E5.5050200>