From owner-freebsd-performance@FreeBSD.ORG Tue Mar 15 15:55:35 2005 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2E2A16A4CE for ; Tue, 15 Mar 2005 15:55:35 +0000 (GMT) Received: from sollube.sarenet.es (sollube.sarenet.es [192.148.167.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CEA443D2F for ; Tue, 15 Mar 2005 15:55:35 +0000 (GMT) (envelope-from BORJAMAR@SARENET.ES) Received: from [127.0.0.1] (matahari.sarenet.es [192.148.167.18]) by sollube.sarenet.es (Postfix) with ESMTP id DB10213A5; Tue, 15 Mar 2005 16:55:33 +0100 (CET) In-Reply-To: <20050315154720.GA69524@stack.nl> References: <20050315153209.GA8863@nipsi.home.net> <20050315154720.GA69524@stack.nl> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1b2fb21a30bde2f07bb8a29f8e389392@SARENET.ES> Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Tue, 15 Mar 2005 16:55:32 +0100 To: Marc Olzheim X-Mailer: Apple Mail (2.619.2) cc: freebsd-performance@freebsd.org Subject: Re: vfs.ufs.dirhash_maxmem is a bit low X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 15:55:36 -0000 On 15 Mar 2005, at 16:47, Marc Olzheim wrote: > On Tue, Mar 15, 2005 at 04:32:09PM +0100, Dennis Berger wrote: >> My request can we add white kernel message for the behavier of >> running out of hashmemory? I'd say stuff it in tuning(7)... My rule of thumb is: In case you have a machine with lots of huge directories (which is _not_ the same as lots of files), in case you see that vfs.ufs.dirhash_mem is very similar to vfs.ufs.dirhash_maxmem, increase vfs.ufs.dirhash_maxmem until you cannot fill it. It's a radical approach, but it gave me very good results in an imap server with lots of maildir folders. Of course, be sure not to run out of memory. Run vmstat and check the "sr" column. Borja.