From owner-freebsd-fs@FreeBSD.ORG Wed Jul 11 14:52:10 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3656116A41F for ; Wed, 11 Jul 2007 14:52:10 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63012.mail.re1.yahoo.com (web63012.mail.re1.yahoo.com [69.147.96.223]) by mx1.freebsd.org (Postfix) with SMTP id E3CA013C43E for ; Wed, 11 Jul 2007 14:52:09 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 26579 invoked by uid 60001); 11 Jul 2007 14:52:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=pLT/dgeKM7Ns4Gxua7ojZEjET4R6QRkN1aAU4XLui4gCZhauV/c1nD6SfpELZW51htAJeP9n7JaVXmJ38UyBybQL7aAodW2UEbENKaN+Vbqhzeo9U/bEemwL0TZK791QETpXbkKr3kQn3id4b157cPmA0f0EiozAfqCYn8V3mU4=; X-YMail-OSG: 7LuVZycVM1k69FTmNmQIxnal.N9haUXzjl8z0qEOiBHGvnFlhymzVnHSEMRaexBj1qPjctYuvBJPwZL45LmMHx.6kT53U8kHlq4w4tYQDDaK06844nCX8SiMZn80_n7g Received: from [71.63.232.32] by web63012.mail.re1.yahoo.com via HTTP; Wed, 11 Jul 2007 07:52:09 PDT Date: Wed, 11 Jul 2007 07:52:09 -0700 (PDT) From: Gore Jarold To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <86847.26083.qm@web63012.mail.re1.yahoo.com> Subject: Re: help needed - tuning a filesystem for rm and cp ? (MORE) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2007 14:52:10 -0000 > > All else being equal, how do you optimize a system for > > copying from one place to another on the same mount > > point ? How do you optimize a system for fast file > > deletion ? Are the two mutually exclusive ? > > You might try increasing vfs.ufs.dirhash_maxmem if the default's too low > for you (see what "sysctl -a | grep dirhash" reports). # sysctl -a | grep dirhash UFS dirhash 895 181K - 550269 16,32,64,128,256,512,1024,2048,4096 vfs.ufs.dirhash_minsize: 2560 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_mem: 2065716 vfs.ufs.dirhash_docheck: 0 Interesting at all ? Above ^^^ is the output for today, but I checked it yesterday as well and got: # sysctl -a | grep dirhash UFS dirhash 180 43K - 452370 16,32,64,128,256,512,1024,2048,4096 vfs.ufs.dirhash_minsize: 2560 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_mem: 860405 vfs.ufs.dirhash_docheck: 0 So do I understand this correctly that right now I am at ~550000 and yesterday I was at ~452000, but yesterday my high water mark was ~860000 and today my high water mark is 2065716 ? So it looks like I maxed it out last night ? ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow