From owner-freebsd-doc@FreeBSD.ORG Fri Apr 22 22:40:17 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80D4616A4D0 for ; Fri, 22 Apr 2005 22:40:17 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1423843D53 for ; Fri, 22 Apr 2005 22:40:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3MMeGPq087565 for ; Fri, 22 Apr 2005 22:40:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3MMeGml087564; Fri, 22 Apr 2005 22:40:16 GMT (envelope-from gnats) Resent-Date: Fri, 22 Apr 2005 22:40:16 GMT Resent-Message-Id: <200504222240.j3MMeGml087564@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Brad Davis Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E878616A4CE for ; Fri, 22 Apr 2005 22:33:04 +0000 (GMT) Received: from ender.liquidneon.com (ender.liquidneon.com [64.78.150.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56F1F43D55 for ; Fri, 22 Apr 2005 22:33:04 +0000 (GMT) (envelope-from bdavis@house.so14k.com) Received: from localhost (localhost [127.0.0.1]) by ender.liquidneon.com (Postfix) with ESMTP id EE5CDA6C1F for ; Fri, 22 Apr 2005 16:33:03 -0600 (MDT) Received: from ender.liquidneon.com ([127.0.0.1]) by localhost (ender.liquidneon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42642-02 for ; Fri, 22 Apr 2005 16:33:03 -0600 (MDT) Received: from mccaffrey.house.so14k.com (gw.house.so14k.com [216.87.87.128]) by ender.liquidneon.com (Postfix) with ESMTP id 6C495A6C1C for ; Fri, 22 Apr 2005 16:33:02 -0600 (MDT) Received: by mccaffrey.house.so14k.com (Postfix, from userid 1001) id E13D9B86C; Fri, 22 Apr 2005 16:33:01 -0600 (MDT) Message-Id: <20050422223301.E13D9B86C@mccaffrey.house.so14k.com> Date: Fri, 22 Apr 2005 16:33:01 -0600 (MDT) From: Brad Davis To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/80267: Add information on tuning kern.maxvnodes X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Brad Davis List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 22:40:17 -0000 >Number: 80267 >Category: docs >Synopsis: Add information on tuning kern.maxvnodes >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Fri Apr 22 22:40:16 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Brad Davis >Release: FreeBSD 5.4-STABLE i386 >Organization: >Environment: System: FreeBSD mccaffrey.house.so14k.com 5.4-STABLE FreeBSD 5.4-STABLE #0: Wed Apr 20 22:22:19 MDT 2005 root@mccaffrey.house.so14k.com:/usr/obj/usr/src/sys/SMP i386 >Description: Add information on tuning kern.maxvnodes. >How-To-Repeat: >Fix: --- doc-ori/en_US.ISO8859-1/books/handbook/config/chapter.sgml Fri Apr 22 11:51:50 2005 +++ doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml Fri Apr 22 15:58:09 2005 @@ -2228,6 +2228,42 @@ + + + Virtual Memory + + + <varname>kern.maxvnodes</varname> + + A vnode is the internal representation of a file or + directory. So increasing the number of vnodes avaliable to + the operating system cuts down on disk I/O. Normally this + is handled by the operating system and does not need to be + changed. In some cases where disk I/O is a bottleneck and + the system is running out of vnodes, this setting will need + to be increased. The amount of inactive and free RAM will + need to be taken into account. + + To see the current number of vnodes in use: + + &prompt.root; sysctl vfs.numvnodes +vfs.numvnodes: 91349 + + To see the maximum vnodes: + + &prompt.root; sysctl kern.maxvnodes +kern.maxvnodes: 100000 + + If the current vnode usage is near the maximum, upping + kern.maxvnodes by a 1,000 is probably a + good idea. Keep an eye on the number of + vfs.numvnodes. If it climbs up to the + maximum again, kern.maxvnodes will need to + be increased further. A shift in your memory usage as + reported by &man.top.1; should be visable. More memory should + be active. + + >Release-Note: >Audit-Trail: >Unformatted: