From owner-freebsd-hackers Mon May 31 5:20: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id DE90D14E66 for ; Mon, 31 May 1999 05:19:56 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 20111 invoked by uid 1001); 31 May 1999 12:19:54 -0000 To: joelh@gnu.org (Joel Ray Holveck) Cc: hackers@freebsd.org Subject: Re: FS tuning (Was: File system gets too fragmented ???) References: <199905271415.HAA10721@salsa.gv.tsc.tdk.com> <86lne8h3gj.fsf@detlev.UUCP> From: Ville-Pertti Keinonen Date: 31 May 1999 15:17:51 +0300 In-Reply-To: joelh@gnu.org's message of "29 May 1999 08:05:16 +0300" Message-ID: <86pv3hph5c.fsf@not.demophon.com> Lines: 15 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG joelh@gnu.org (Joel Ray Holveck) writes: > As we all know, tunefs -o space will hurt write performance. Will it > hurt read performance? If I don't care about install-time speed, but > do care about run-time speed and free space, should I populate my > filesystems at install time with space tuning? -o space should have very little effect install-time. The space vs. time optimization parameter only has any effect when files are extended by small amounts (the fragment at the end is reallocated). This seldom happens for most files. Log files and interactively edited files are probably (just guessing) most likely to make use of fragment reallocations. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message