From owner-freebsd-isp Mon Aug 26 10:42:38 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26685 for isp-outgoing; Mon, 26 Aug 1996 10:42:38 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA26676 for ; Mon, 26 Aug 1996 10:42:34 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA00675; Mon, 26 Aug 1996 12:41:22 -0500 From: Joe Greco Message-Id: <199608261741.MAA00675@brasil.moneng.mei.com> Subject: Re: Anyone using ccd (FreeBSD disk striper) for news To: alk@think.com (Tony Kimball) Date: Mon, 26 Aug 1996 12:41:22 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, freebsd-isp@FreeBSD.ORG In-Reply-To: <199608261736.MAA10693@compound.Think.COM> from "Tony Kimball" at Aug 26, 96 12:36:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Quoth Joe Greco on Mon, 26 August: > : I've played with metadata updates before (disabled ATIME and MTIME updates) > : but I don't want to do it on a production system until there is an > : officially sanctioned method to do so. > > As I understand it, this is like half way to an async mount? It's more like half way to a -ro mount. Sometimes you do not CARE when someone last read a file. It costs lots and lots of disk bandwidth to write that information back on a busy news server where thousands of files are accessed during every 30 second interval. If you do not have to write that information, you now have more disk bandwidth with which to READ more data, which is what you really wanna do. ... JG