Date: Mon, 02 Aug 2004 19:11:03 -0600 From: Scott Long <scottl@freebsd.org> To: "David E. O'Brien" <obrien@freebsd.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c Message-ID: <410EE627.8090105@freebsd.org> In-Reply-To: <200408022152.i72Lqhig042925@repoman.freebsd.org> References: <200408022152.i72Lqhig042925@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David E. O'Brien wrote: > obrien 2004-08-02 21:52:43 UTC > > FreeBSD src repository > > Modified files: > sys/kern vfs_subr.c > Log: > Put a cap on the auto-tuning of kern.maxvnodes. > > Cap value chosen by: scottl > > Revision Changes Path > 1.518 +8 -0 src/sys/kern/vfs_subr.c Well, the number that I gave was really only a suggestion and is far too low to be useful on in a production environment like squid or a mail/imap server. What we should really be doing is scaling based on the size of the kmem_map. We should also be scaling kmem_map based on the size of physical RAM and not capping it to such relatively low values like we do right now. I'm also quite afraid of what might happen to something like squid that will be exerting both vnode and mbug pressure at the same time. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?410EE627.8090105>