From owner-freebsd-hackers Sun Jan 12 11:06:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA11383 for hackers-outgoing; Sun, 12 Jan 1997 11:06:44 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA11378 for ; Sun, 12 Jan 1997 11:06:42 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id OAA13998; Sun, 12 Jan 1997 14:05:53 -0500 (EST) From: Charles Henrich Message-Id: <199701121905.OAA13998@crh.cl.msu.edu> Subject: Re: mount -o async on a news servre To: terry@lambert.org (Terry Lambert) Date: Sun, 12 Jan 1997 14:05:53 -0500 (EST) Cc: terry@lambert.org, freebsd-hackers@freebsd.org In-Reply-To: <199701121851.LAA25856@phaeton.artisoft.com> from Terry Lambert at "Jan 12, 97 11:51:35 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Sorry; you are mistaken. > > The "noatime" option says not to act on access time update events. > > The majority of FS updates that result from read activity are the > access time being updated on getdents() calls in opendir/readdir; > a Minor number of access events are generated for the article files > themselves. > > You seem to be confusing "noatime" with "async". The "async" option > acts pretty much as you describe. You've misread what I said. Using atime with sync's done every 300 seconds I would beleive is very similar in performance to async, without the risks. This is of course only in the case of a news spool. > You could rephrase this as "Is there any safe way to run 'async'?", > with the answer being "Yes, if you only read from, and never post > directly to, the 'async' server". No No, perhaps I wasnt clear. I was never advocating running async, its a big bad idea IMHO. I was attempting to show that running with noatime and sync's pushed back to be infrequent (300 seconds) you get nearly the performance win of async, without the risks.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich