From bdavis@house.so14k.com  Fri Apr 22 22:33:04 2005
Return-Path: <bdavis@house.so14k.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E878616A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; 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 <FreeBSD-gnats-submit@freebsd.org>; 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 <FreeBSD-gnats-submit@freebsd.org>; 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 <FreeBSD-gnats-submit@freebsd.org>;
 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 <FreeBSD-gnats-submit@freebsd.org>; 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 <so14k@so14k.com>
Reply-To: Brad Davis <so14k@so14k.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Add information on tuning kern.maxvnodes 
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         80267
>Category:       docs
>Synopsis:       Add information on tuning kern.maxvnodes
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    jcamou
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr 22 22:40:16 GMT 2005
>Closed-Date:    Sun Apr 24 03:16:38 GMT 2005
>Last-Modified:  Sun Apr 24 03:16:38 GMT 2005
>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 @@
 	</note>
       </sect3>
     </sect2>
+
+    <sect2>
+      <title>Virtual Memory</title>
+
+      <sect3>
+        <title><varname>kern.maxvnodes</varname></title>
+
+        <para>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.</para>
+
+        <para>To see the current number of vnodes in use:</para>
+
+        <programlisting>&prompt.root; sysctl vfs.numvnodes
+vfs.numvnodes: 91349</programlisting>
+
+        <para>To see the maximum vnodes:</para>
+
+        <programlisting>&prompt.root; sysctl kern.maxvnodes
+kern.maxvnodes: 100000</programlisting>
+
+        <para>If the current vnode usage is near the maximum, upping
+          <varname>kern.maxvnodes</varname> by a 1,000 is probably a
+          good idea.  Keep an eye on the number of
+          <varname>vfs.numvnodes</varname>.  If it climbs up to the
+          maximum again, <varname>kern.maxvnodes</varname> 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.</para>
+      </sect3>
+    </sect2>
   </sect1>
 
   <sect1 id="adding-swap-space">
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-doc->jcamou  
Responsible-Changed-By: jcamou 
Responsible-Changed-When: Fri Apr 22 22:49:58 GMT 2005 
Responsible-Changed-Why:  
Over to me. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=80267 

From: Brad Davis <so14k@so14k.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/80267: Add information on tuning kern.maxvnodes
Date: Fri, 22 Apr 2005 17:10:38 -0600

 Fix a typo and professionalize some wording noticed by jcamou@
 
 
 --- 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 17:08:09 2005
 @@ -2228,6 +2228,42 @@
  	</note>
        </sect3>
      </sect2>
 +
 +    <sect2>
 +      <title>Virtual Memory</title>
 +
 +      <sect3>
 +        <title><varname>kern.maxvnodes</varname></title>
 +
 +        <para>A vnode is the internal representation of a file or
 +          directory.  So increasing the number of vnodes available 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.</para>
 +
 +        <para>To see the current number of vnodes in use:</para>
 +
 +        <programlisting>&prompt.root; sysctl vfs.numvnodes
 +vfs.numvnodes: 91349</programlisting>
 +
 +        <para>To see the maximum vnodes:</para>
 +
 +        <programlisting>&prompt.root; sysctl kern.maxvnodes
 +kern.maxvnodes: 100000</programlisting>
 +
 +        <para>If the current vnode usage is near the maximum, increasing
 +          <varname>kern.maxvnodes</varname> by a 1,000 is probably a
 +          good idea.  Keep an eye on the number of
 +          <varname>vfs.numvnodes</varname>.  If it climbs up to the
 +          maximum again, <varname>kern.maxvnodes</varname> 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.</para>
 +      </sect3>
 +    </sect2>
    </sect1>
  
    <sect1 id="adding-swap-space">
 

From: Brad Davis <so14k@so14k.com>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: docs/80267: Add information on tuning kern.maxvnodes
Date: Sat, 23 Apr 2005 16:47:45 -0600

 Improve wording, noticed by will@
 
 s/by a 1,000/by a value of 1,000/
 
 
 --- 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	Sat Apr 23 16:45:14 2005
 @@ -2228,6 +2228,42 @@
  	</note>
        </sect3>
      </sect2>
 +
 +    <sect2>
 +      <title>Virtual Memory</title>
 +
 +      <sect3>
 +        <title><varname>kern.maxvnodes</varname></title>
 +
 +        <para>A vnode is the internal representation of a file or
 +          directory.  So increasing the number of vnodes available 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.</para>
 +
 +        <para>To see the current number of vnodes in use:</para>
 +
 +        <programlisting>&prompt.root; sysctl vfs.numvnodes
 +vfs.numvnodes: 91349</programlisting>
 +
 +        <para>To see the maximum vnodes:</para>
 +
 +        <programlisting>&prompt.root; sysctl kern.maxvnodes
 +kern.maxvnodes: 100000</programlisting>
 +
 +        <para>If the current vnode usage is near the maximum, increasing
 +          <varname>kern.maxvnodes</varname> by a value of 1,000 is
 +          probably a good idea.  Keep an eye on the number of
 +          <varname>vfs.numvnodes</varname>.  If it climbs up to the
 +          maximum again, <varname>kern.maxvnodes</varname> 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.</para>
 +      </sect3>
 +    </sect2>
    </sect1>
  
    <sect1 id="adding-swap-space">

From: Brad Davis <so14k@so14k.com>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: docs/80267: Add information on tuning kern.maxvnodes
Date: Sat, 23 Apr 2005 16:50:27 -0600

 Fix a spelling error, also noticed by will@
 
 
 
 --- 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	Sat Apr 23 16:48:24 2005
 @@ -2228,6 +2228,42 @@
  	</note>
        </sect3>
      </sect2>
 +
 +    <sect2>
 +      <title>Virtual Memory</title>
 +
 +      <sect3>
 +        <title><varname>kern.maxvnodes</varname></title>
 +
 +        <para>A vnode is the internal representation of a file or
 +          directory.  So increasing the number of vnodes available 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.</para>
 +
 +        <para>To see the current number of vnodes in use:</para>
 +
 +        <programlisting>&prompt.root; sysctl vfs.numvnodes
 +vfs.numvnodes: 91349</programlisting>
 +
 +        <para>To see the maximum vnodes:</para>
 +
 +        <programlisting>&prompt.root; sysctl kern.maxvnodes
 +kern.maxvnodes: 100000</programlisting>
 +
 +        <para>If the current vnode usage is near the maximum, increasing
 +          <varname>kern.maxvnodes</varname> by a value of 1,000 is
 +          probably a good idea.  Keep an eye on the number of
 +          <varname>vfs.numvnodes</varname>.  If it climbs up to the
 +          maximum again, <varname>kern.maxvnodes</varname> will need to
 +          be increased further.  A shift in your memory usage as
 +          reported by &man.top.1; should be visible.  More memory should
 +          be active.</para>
 +      </sect3>
 +    </sect2>
    </sect1>
  
    <sect1 id="adding-swap-space">
State-Changed-From-To: open->closed  
State-Changed-By: jcamou 
State-Changed-When: Sun Apr 24 03:16:11 GMT 2005 
State-Changed-Why:  
Committed, thanks! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=80267 
>Unformatted:
