From owner-freebsd-current Fri Sep 25 14:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19289 for freebsd-current-outgoing; Fri, 25 Sep 1998 14:54:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-20.ppp.wenet.net [206.15.84.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19282 for ; Fri, 25 Sep 1998 14:54:26 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id OAA01227; Fri, 25 Sep 1998 14:56:08 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 25 Sep 1998 14:56:08 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Mark Mayo cc: current Subject: Re: shouting in a void? In-Reply-To: <19980925153626.A9927@vmunix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 25 Sep 1998, Mark Mayo wrote: [...] > It will have 7200rpm Seagate cudas. And unless they've got a few disks > striped (preferably in an array) they will thrash and be "nailed to the wall" > just like freefall. And given the fact that doing a stat() seems to take > forever on Solaris, plus the slower drive, I'd wager on a single disk freefall > would eat it up. :-) The enterprise prolly has as much RAM or more than freefall, so I would assume some of that RAM might be used as a disk cache.. thus caching stat() info. Although in reality, it does preform quite horribly in general with cvsup (could be the precompiled binary), I never thought of the disks as the bottleneck.. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message