Xref: utzoo comp.unix.sysv386:2752 comp.unix.questions:27396 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!helps!uudell!bigtex!james From: james@bigtex.cactus.org (James Van Artsdalen) Newsgroups: comp.unix.sysv386,comp.unix.questions Subject: Re: Tuning SYSVR3 (Esix Rev D) (LONG!) Message-ID: <50739@bigtex.cactus.org> Date: 6 Dec 90 02:40:36 GMT References: <1990Dec02.001311.16727@virtech.uucp> <1990Dec4.031037.2718@jwt.UUCP> <1990Dec4.162751.12224@bilv Reply-To: james@bigtex.cactus.org (James Van Artsdalen) Followup-To: comp.unix.sysv386 Organization: Institute of Applied Cosmology, Austin TX Lines: 15 In <1990Dec4.162751.12224@bilver.uucp>, bill@bilver.UUCP (Bill Vermillion) wrote: > I can't tell you what takes priority in a caching controller, but I will > tell you this, it more than makes a system feel snappy. One effect is that writes are no longer synchronous. AT&T's concept of file system hardening is to do the writes in a certain order, waiting for each to finish. A caching controller with a write-back cache makes something like "rm *" much faster since no actual I/O happens until later. You do sacrifice some filesystem recoverability though. -- James R. Van Artsdalen james@bigtex.cactus.org "Live Free or Die" Dell Computer Co 9505 Arboretum Blvd Austin TX 78759 512-338-8789