From owner-freebsd-hackers Wed Sep 2 18:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12963 for freebsd-hackers-outgoing; Wed, 2 Sep 1998 18:13:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12958 for ; Wed, 2 Sep 1998 18:13:37 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA21641; Wed, 2 Sep 1998 18:12:35 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd021620; Wed Sep 2 18:12:28 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA02792; Wed, 2 Sep 1998 18:12:26 -0700 (MST) From: Terry Lambert Message-Id: <199809030112.SAA02792@usr07.primenet.com> Subject: Re: Reading/writing /usr/ports is VERY slow To: cmascott@world.std.com (Carl Mascott) Date: Thu, 3 Sep 1998 01:12:26 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199809022252.SAA00872@europa.local> from "Carl Mascott" at Sep 2, 98 06:52:59 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, > if a cg proximity criterion were added to the new-cg-chooser, > then the size of a cg would become a factor, although I don't > know how important a factor. Very important. It would result in FFS finally adding "support" for fragmenting the bejesus out of a disk drive. This would be a *very* bad thing. > Hopefully someone who knows the history of FFS development > will chime in at this point. It would be nice to know if > any other directory placement policies were ever tried and > rejected. The original "free reserve" values were set to 10% for a reason; it was a compromise between people who wanted to use every byte, and the actual 15% value required for a "perfect hash". In effect, when the FS picks a block (or, more correctly, a cluster), it is hashing the filespace onto the disk. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message