From owner-freebsd-fs Sat Oct 19 12:42:54 1996 Return-Path: owner-fs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29581 for fs-outgoing; Sat, 19 Oct 1996 12:42:54 -0700 (PDT) Received: from brimstone.gage.com (brimstone.gage.com [205.217.2.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA29576 for ; Sat, 19 Oct 1996 12:42:46 -0700 (PDT) Received: (from mail@localhost) by brimstone.gage.com (8.7.5/8.7.3) id OAA18058; Sat, 19 Oct 1996 14:41:53 -0500 (CDT) Received: from octopus.gage.com(158.60.57.50) by brimstone.gage.com via smap (V2.0beta) id xma018056; Sat, 19 Oct 96 14:41:28 -0500 Received: from squid.gage.com (squid [158.60.57.101]) by octopus.gage.com (8.7.5/8.7.3) with SMTP id OAA10491; Sat, 19 Oct 1996 14:35:32 -0500 (CDT) Received: from insomnia by squid.gage.com (NX5.67e/NX3.0S) id AA01614; Sat, 19 Oct 96 14:42:14 -0500 Message-Id: <9610191942.AA01614@squid.gage.com> Received: by insomnia.gage.com (NX5.67g/NX3.0X) id AA02041; Sat, 19 Oct 96 14:42:30 -0500 Mime-Version: 1.0 (NeXT Mail 4.0 v146.2) Content-Type: multipart/alternative; boundary=NeXT-Mail-466589079-1 Content-Transfer-Encoding: 7bit In-Reply-To: X-Nextstep-Mailer: Mail 3.3 (Enhance 1.3) Received: by NeXT.Mailer (1.146.2) From: Ben Black Date: Sat, 19 Oct 96 14:42:29 -0500 To: "Matthew N. Dodd" Subject: Re: ccd setup for striping Cc: fs@freebsd.org References: Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --NeXT-Mail-466589079-1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline >When you have 150,000 customers news is a high availability application. >(I don't have this problem yet, but know people who do.) when you have 150k customers you have more than one news server. >I'd like to see your hard numbers as to the 'software RAID killing >performance'. Its had the opposite effect here. Of course, we're not >running RAID5, just interleaving. "just interleaving" doesn't give you any redundancy, now does it? RAID 5 is all about parity calculations. we used sun online disk suite to do a software RAID on one of several news servers. performance was far better simply distributing the news groups across drives intelligently. >I'm sorry, but a high end news server is seek bound. > >Run some tests on a test platform before you make statements about >performance. yes, assuming you aren't recalculating parity every time to read or write data, it is seek bound. to eliminate the massive seek bottleneck, get rid of the filesystem. that's what we did. as i've said before, 6 million articles per day on a P5-120 with 64MB RAM. then we ran out of articles. load average under 2.0. i know about new server performance. any questions? b3n --NeXT-Mail-466589079-1 Content-Type: text/enriched; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline >When you have 150,000 customers news is a high availability application. >(I don't have this problem yet, but know people who do.) when you have 150k customers you have more than one news server. >I'd like to see your hard numbers as to the 'software RAID killing >performance'. Its had the opposite effect here. Of course, we're not >running RAID5, just interleaving. "just interleaving" doesn't give you any redundancy, now does it? RAID 5 is all about parity calculations. we used sun online disk suite to do a software RAID on one of several news servers. performance was far better simply distributing the news groups across drives intelligently. >I'm sorry, but a high end news server is seek bound. > >Run some tests on a test platform before you make statements about >performance. yes, assuming you aren't recalculating parity every time to read or write data, it is seek bound. to eliminate the massive seek bottleneck, get rid of the filesystem. that's what we did. as i've said before, 6 million articles per day on a P5-120 with 64MB RAM. then we ran out of articles. load average under 2.0. i know about new server performance. any questions? b3n --NeXT-Mail-466589079-1--