From owner-freebsd-arch Mon Oct 15 23: 2:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id DFCF437B405; Mon, 15 Oct 2001 23:02:44 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA27735; Tue, 16 Oct 2001 16:02:29 +1000 Date: Tue, 16 Oct 2001 16:01:40 +1000 (EST) From: Bruce Evans X-X-Sender: To: Matt Dillon Cc: Ollivier Robert , Peter Wemm , "David O'Brien" , , Subject: Re: cvs commit: src/sbin/newfs newfs.8 newfs.c In-Reply-To: <200110151607.f9FG7QL54919@earth.backplane.com> Message-ID: <20011016154235.N6619-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 15 Oct 2001, Matt Dillon wrote: > note: we shouldn't default to anything other then 8K/1K or 16K/2K. No > other combinations are optimal at the moment. This depends on the mix of file sizes, and probably on the drive. My benchmarks (made just after the dirpref changes) showed that 4K/2K, 8K/2K and 16K/2K are optimal for holding /usr/src, as measured by tarring up the src tree on a freshly mounted filesystem after just having written the src tree to an empty filesystem (the write speed is relatively sensitive to the layout). This is presumably caused by the average fragment size being related to 2K. ffs-4096-512: tar cf /dev/null src: 51.50 real 1.09 user 12.61 sys ffs-4096-1024: tar cf /dev/null src: 39.77 real 1.17 user 12.16 sys ffs-4096-2048: tar cf /dev/null src: 37.29 real 1.26 user 12.51 sys ffs-4096-4096: tar cf /dev/null src: 38.92 real 1.00 user 12.51 sys ffs-8192-1024: tar cf /dev/null src: 39.39 real 1.07 user 11.27 sys ffs-8192-2048: tar cf /dev/null src: 32.90 real 0.89 user 11.50 sys ffs-8192-4096: tar cf /dev/null src: 33.53 real 1.02 user 11.33 sys ffs-8192-8192: tar cf /dev/null src: 37.85 real 1.10 user 11.54 sys ffs-16384-2048: tar cf /dev/null src: 28.47 real 1.09 user 10.76 sys ffs-16384-4096: tar cf /dev/null src: 29.64 real 1.12 user 10.86 sys ffs-16384-8192: tar cf /dev/null src: 32.67 real 0.98 user 10.83 sys ffs-16384-16384: tar cf /dev/null src: 44.43 real 1.07 user 11.24 sys Note that the extremes of 4K:512 and 16K:16K are the worst, despite 4K:512 having the 8:1 ratio. The filesystem for this test was rather small (about 1GB) IIRC. Larger block sizes work relatively better for larger filesystems, not because they can be accessed more efficiently (clustering makes this advantage small), but because they reduce the number of cylinder groups by a small factor. The dirpref changes reduced this advantage significantly. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message